[Q] Nexus s stuck on Google Screen - Nexus S Q&A, Help & Troubleshooting

My Nexus s i9020T is stuck on the google screen. I was trying to root it and when it was done my phone rebooted and it got stuck on the google screen. My bootloader is unlocked and i was running on gingerbread 2.3.6 can somebody tell me how to resolve this issue using a mac

How long did you waited? Sometimes that Google logo could tale a long time. Try going through the root process again
Sent from my Nexus S using Tapatalk 2

Same problem
I got the same problem. i can access recovery mode but my phone is not getting detected in PC. just hangs on Google logo (white) :crying:
bootloader os locked also.
My Model is GT-I9020T.
please help.
thanks in advance.

You should try the usb jig sold on ebay for the Nexus S.. It will bring the phone to download mode so you can flash your firmware with odin.. To use odin on your mac you need to have Windows installed with a virtual machine or virtualbox..
---------- Post added at 03:40 AM ---------- Previous post was at 03:35 AM ----------
Kumar Anil said:
I got the same problem. i can access recovery mode but my phone is not getting detected in PC. just hangs on Google logo (white) :crying:
bootloader os locked also.
My Model is GT-I9020T.
please help.
thanks in advance.
Click to expand...
Click to collapse
Bad luck for you.. Since your bootloader is locked and you can't unlock it you can't do anything.. Also you are talking about stock Android recovery right..? No TWRP or CWM..?

same problem
thanks for replying.
actually
I have google nexus GT-I9020t. it hangs on google logo (white). fastboot oem unlock is not working. lock state : locked.
when i go into recovery mode and try to wipe data/factory reset, it says:
e:format_volume: make_extf4fs failed on /dev/block/platform/s3c-sdhc1.0/byname/userdata
if i try to flash using fastboot, it says run fastboot oem unlock command.
it is not detecting in odin also. i have installed the drivers though.
else it is going to recovery mode, showing the lock status and i can also go futher in format, data wipe menu.
anything i can purchase will help or not, i dont know.
please help.

Kumar Anil said:
thanks for replying.
actually
I have google nexus GT-I9020t. it hangs on google logo (white). fastboot oem unlock is not working. lock state : locked.
when i go into recovery mode and try to wipe data/factory reset, it says:
e:format_volume: make_extf4fs failed on /dev/block/platform/s3c-sdhc1.0/byname/userdata
if i try to flash using fastboot, it says run fastboot oem unlock command.
it is not detecting in odin also. i have installed the drivers though.
else it is going to recovery mode, showing the lock status and i can also go futher in format, data wipe menu.
anything i can purchase will help or not, i dont know.
please help.
Click to expand...
Click to collapse
I made a USB JIG And its showing me some screen. please Check and update.

Kumar Anil said:
I made a USB JIG And its showing me some screen. please Check and update.
Click to expand...
Click to collapse
I remember this screen when I first rooted my Nexus S GTi9023. About the Google logo keep showing, phone probably not finding correct bootloader. I have this issue when I tried jellyBam rom. Fortunalty I had the nandroid back up of other roms that I have tried and I pick up then CM 10.1.2 and choose its backup file for restoring bootloader. Here you me also flash bootloader from PC as well as.

vikaskanani said:
I remember this screen when I first rooted my Nexus S GTi9023. About the Google logo keep showing, phone probably not finding correct bootloader. I have this issue when I tried jellyBam rom. Fortunalty I had the nandroid back up of other roms that I have tried and I pick up then CM 10.1.2 and choose its backup file for restoring bootloader. Here you me also flash bootloader from PC as well as.
Click to expand...
Click to collapse
But how to flash a bootloader? when i try "fastboot oem unlock" it fails. and when it is locked i cant flash a bootloader. any suggestions?

Kumar Anil said:
But how to flash a bootloader? when i try "fastboot oem unlock" it fails. and when it is locked i cant flash a bootloader. any suggestions?
Click to expand...
Click to collapse
You need to accept the warning message, the screen you attached.
Have a look at redmondpie.com/unlock-nexus-s-bootloader-how-to-guide/ (sorry cant post link as i am new user)
As I said, its been a long time, since I rooted, so I guess, you need to use power key or volume key for any action.

fastboot oem unlock not working
vikaskanani said:
You need to accept the warning message, the screen you attached.
Have a look at redmondpie.com/unlock-nexus-s-bootloader-how-to-guide/ (sorry cant post link as i am new user)
As I said, its been a long time, since I rooted, so I guess, you need to use power key or volume key for any action.
Click to expand...
Click to collapse
I guess, USB debugging mode was not checked at the time of the crash. It is detecting in the fastboot devices command but not in ADB devices.
i did everything in the link, you provided me.
and any other way to force partion of somthing. Any Other Option.
FATSBOOT OEM COMMAND:
http://s10.postimg.org/r0rjcrxe1/fastboot_oem_failed.jpg
thanks in advance

Can you boot in jelly bean?? Strange issue!
Sent from my Nexus 7 using xda app-developers app

Related

[Q] Stuck in "FASTBOOT MODE - NO BOOT OR RECOVERY IMG"

My NExus S is stuck on the screen that says:
Fastboot Mode No Boot or Recovery IMg.
Product Name - Herring
HW Version - Rev34
Bootloader Version - D720SPRKC5
Baseband Version - D720SPRLCI
Carrier Inro - SPR
Serial Number 32300E25C33500EC
Lock State - Locked
options to select
Reboot Bootloader (gives me exact same screen) except it only says "Fastboot"
Reboot Back to the "FASTBOOT MODE - NO BOOT OR RECOVERY IMG"
Recovery (Can boot to CWM but I can't mount anything)
Power OFF (That works fine)
Then the little green man and the android logo
Followed by USB Control INIT
USB Control INIT End
STANDARD_SET_CONFIGURATION
Conventional wisdom says download some files and fix via fastboot. However in fastbootI can't run ANY of the steps without running FASTBOOT OEM UNLOCK. When I run it my phone asks if I really want to unlock the bootloader. when I choose YEs and hit power it just freezes there.
My next thought Boot to recovery and restore. A restore through recovery followed by a reboot leads me back to the original no boot or recovery img.
Okay I'll just sideload a working rom by mounting usb storage. Then I can flash it with CWM and be up and running.
but when I try to do mount the USB Storage I get "E:Unable to write to ums 1unfile (No such file or directory)"
Finally, Last ditch Effort, I'll load up ODIN and use that to put on a working recovery. there's forums all over the place explaining how to do that right? Well yes, but the links to the Tar file are all broken.
What next my friends? I'd really like to get this phone working.
Wug's Nexus Root Toolkit.
ej8989 said:
Wug's Nexus Root Toolkit.
Click to expand...
Click to collapse
I tried doing the Flash stock + unroot in wug's kit but no luc. any other ideas?
swing4thefence said:
I tried doing the Flash stock + unroot in wug's kit but no luc. any other ideas?
Click to expand...
Click to collapse
Your bootloader is LOCKED. You must first UNLOCK the bootloader by clicking "Unlock" on Nexus Root Toolkit.
ej8989 said:
Your bootloader is LOCKED. You must first UNLOCK the bootloader by clicking "Unlock" on Nexus Root Toolkit.
Click to expand...
Click to collapse
No matter how I try to do it, it always freezes at the unlock bootloader step.
Did you install proper drivers?
ej8989 said:
Did you install proper drivers?
Click to expand...
Click to collapse
I thought so. My wife is on the computer so if she ever gives it back I'll re-install the drivers and try again.
swing4thefence said:
I thought so. My wife is on the computer so if she ever gives it back I'll re-install the drivers and try again.
Click to expand...
Click to collapse
Reinstalled Drivers. Still no luck.
I have the same problem.
Same situation for me, because i pressed "Reboot" in CWM without having flashed a Rom (stupid ). Broken power button, hanging on Google logo or in Fastboot mode.
I hope RTK will help me :good: :laugh:
Edit: I have no idea how to revive my Nexus S. Status: Broken Power button, Bootloop, can access Fastbood Mode but dont select someting, Bootloader unlocked, RTK doesn´t find any devices in Fastboot Mode, Device is rooted and has CWM
!Lür said:
Same situation for me, because i pressed "Reboot" in CWM without having flashed a Rom (stupid ). Broken power button, hanging on Google logo or in Fastboot mode.
I hope RTK will help me :good: :laugh:
Edit: I have no idea how to revive my Nexus S. Status: Broken Power button, Bootloop, can access Fastbood Mode but dont select someting, Bootloader unlocked, RTK doesn´t find any devices in Fastboot Mode, Device is rooted and has CWM
Click to expand...
Click to collapse
what about just using adb? Can you find it when you type fastboot devices? If so there's a command in fastboot to reboot to recovery I think.
I on the other hand am screwed. I read in another forum that it hangs on unlock because the internal memory is fubar.
swing4thefence said:
what about just using adb? Can you find it when you type fastboot devices? If so there's a command in fastboot to reboot to recovery I think.
I on the other hand am screwed. I read in another forum that it hangs on unlock because the internal memory is fubar.
Click to expand...
Click to collapse
Solution for me:
1. Turn device on into Bootloop
2. Connect it via USB (PC founds it)
3. type in CMD "adb reboot recovery"
4. device is in recovery
5. reflash everything i wanted :good:
Requirement is a working Android-SDK!
I wish it was that easy for me. I can access recovery just fine. It's the memory I can't touch. Unless someone knows a way to fix corrupted memory...
Sent from my SCH-I510 using xda app-developers app
Im having this same issue too i can still get to CWM recovery but nothing really helps from there. I can still mount my storage and put zip files on there etc but nothing seems to fix the problem...any progress?
swing4thefence said:
I wish it was that easy for me. I can access recovery just fine. It's the memory I can't touch. Unless someone knows a way to fix corrupted memory...
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
I think I'm going to try using my computer to mount and format the internal memory. any ideas as to the correct settings to use when I try this? at this point what have I got to lose?
swing4thefence said:
I think I'm going to try using my computer to mount and format the internal memory. any ideas as to the correct settings to use when I try this? at this point what have I got to lose?
Click to expand...
Click to collapse
Was this solved by any means ??, i am myself stuck at that position
Flash the stock image again using the Nexus Toolkit
Sent from my Nexus S using xda app-developers app
Akbar89 said:
Flash the stock image again using the Nexus Toolkit
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Wug's Nexus toolkit ?? It is stuck on bootloader unlock menu, as unlocking bootloader makes it freeze. Without unlock it doesn't flashI anything.
If there is another tool please guide me with link.
Avoid Spells!!! "Auto correct : ON"
stuck on fastboot mode(lenovo S860)
recently i've bought lenovo s860 (2GB version).....its latest updates had bugs....so i was trying to downgrade to lower version(jelly bean).....in the way i got stuck in fastboot mode......is there any way to get out of it??
same problem in galaxy nexus i9250m
ej8989 said:
Did you install proper drivers?
Click to expand...
Click to collapse
i have same problem in galaxy nexus i9250m
my bootloader showingh no boot or recovery img
i have working fastboot, workin adb and driver
my oem is unlocked with fastboot
bt i am unable to flash recovery and rom

[Q] Where has recovery gone?

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!

[Q] Can't boot, recovery keeps dissapearing

I have searched and tried different things but I'm getting nowhere. I have been running Purity rom on this for a while but when I woke up this morning, I found my screen black and only being able to boot to the bootloader and and google screen (which quickly goes away and goes black again). When I tried to go to recovery at first I believe it was just shutting off. Now it goes to a light black screen.
The first thing I did was flashed the factory image .bat file and everything seemed to go ok but when trying to go to recovery after it went to the light black screen. I turned it off and it booted to the Google screen then off again. Then it booted to the google screen and it froze that way. I can always get it back to the bootloader screen and got it to recovery once by flashing TWRP again using ADB.
TWRP opened once and I tried to do a factory reset but it couldn't find anything and couldn't mount to anything. I got it back to the bootloader again but the recovery has disappeared again. I tried to flash the factory image again but it definitely failed this time.
Please help.
aburn95 said:
I have searched and tried different things but I'm getting nowhere. I have been running Purity rom on this for a while but when I woke up this morning, I found my screen black and only being able to boot to the bootloader and and google screen (which quickly goes away and goes black again). When I tried to go to recovery at first I believe it was just shutting off. Now it goes to a light black screen.
The first thing I did was flashed the factory image .bat file and everything seemed to go ok but when trying to go to recovery after it went to the light black screen. I turned it off and it booted to the Google screen then off again. Then it booted to the google screen and it froze that way. I can always get it back to the bootloader screen and got it to recovery once by flashing TWRP again using ADB.
TWRP opened once and I tried to do a factory reset but it couldn't find anything and couldn't mount to anything. I got it back to the bootloader again but the recovery has disappeared again. I tried to flash the factory image again but it definitely failed this time.
Please help.
Click to expand...
Click to collapse
@bitdomo might be able to help you lol
Might be bad eMMC or something?
when youre flashing recovery, which command are you using.. fastboot boot recovery recoveryname.img or fastboot flash recovery recoveryname.img?
aburn95 said:
I have searched and tried different things but I'm getting nowhere. I have been running Purity rom on this for a while but when I woke up this morning, I found my screen black and only being able to boot to the bootloader and and google screen (which quickly goes away and goes black again). When I tried to go to recovery at first I believe it was just shutting off. Now it goes to a light black screen.
The first thing I did was flashed the factory image .bat file and everything seemed to go ok but when trying to go to recovery after it went to the light black screen. I turned it off and it booted to the Google screen then off again. Then it booted to the google screen and it froze that way. I can always get it back to the bootloader screen and got it to recovery once by flashing TWRP again using ADB.
TWRP opened once and I tried to do a factory reset but it couldn't find anything and couldn't mount to anything. I got it back to the bootloader again but the recovery has disappeared again. I tried to flash the factory image again but it definitely failed this time.
Please help.
Click to expand...
Click to collapse
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
simms22 said:
when youre flashing recovery, which command are you using.. fastboot boot recovery recoveryname.img or fastboot flash recovery recoveryname.img?
Click to expand...
Click to collapse
Hey I'm using "fastboot flash recovery recovery.img" and that's what I've used in the past. I've had a fully functioning rom with fully functioning recovery for a while until yesterday.
bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Ok thanks I'll try this and check the text in fastboot after work today. Thanks for the responses guys.
After reading some more last night I'm afraid it's an emmc problem but I like to be proven wrong sometimes.
Maybe also try this?
http://forum.xda-developers.com/showthread.php?t=2577447
beekay201 said:
Maybe also try this?
http://forum.xda-developers.com/showthread.php?t=2577447
Click to expand...
Click to collapse
I actually have that thread open on my computer. It was my next attempt of repair before starting the thread late last night. Thanks for the suggestion I will certainly try it.
Update: I tried pushing Philz recovery to the phone which seemed to work fine until I selected go to recovery mode. It just went back to that barely light black screen. I'll try again when I get home. Going to try Bitdomo's advice about locking bootloader first.
bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Out of curiosity what's the reason for using two brands, or were they just available so they were used?
bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Bitdomo I'm trying the Flashtool but it's staying at 0% on the firmware update and nothing is popping up on computer or in Device Manager. Had no connection issues prior to the brick or with adb/fastboot. My Ports aren't evening showing at all in DM even if I select show hidden devices.
aburn95 said:
How do I lock the bootloader without being able to put the .zip on my internal memory?
Click to expand...
Click to collapse
In fastboot type
fastboot oem lock
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
In fastboot type
fastboot oem lock
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I honestly wanted to do that but it seemed too easy. I was trying to lock it like I did before when i had to send original back to T-Mobile. Sorry and thanks.
bitdomo said:
Lock your bootloader then reboot to fastboot. If the lock state remains locked try LG flashtool. Link in my signature. If the lock state reverts back to unlocked, then you have to rma your device. If that is the case can you check the variant text in fastboot for me? There should be D820 or D821 and after there should be a letter E or H in (). I want to know that letter in the (). Thanks.
Dont forget to report me your progress
Click to expand...
Click to collapse
Ok so it stayed locked so that's a start. I'm back in download mode again but it's staying at 0% and nothing on computer.
I tried to re-download the factory images and flash again using adb. It failed again. Here's a picture of what happened:
Unzip the zip and use manual flash commands. Clikc the link in my signature and read my "adb and fastboot. What is it?" thread of you're unsure of the commands.
Sent from my Nexus 5 using Tapatalk
aburn95 said:
I tried to re-download the factory images and flash again using adb. It failed again. Here's a picture of what happened:
Click to expand...
Click to collapse
You have "remote: flash write failure" error. It means your emmc (internal storage) is broken and you cannot modify the data on it. You have to rma your device.
Just for matter of research can you enter to fastboot and post the variable line here?
Mine is: hammerhead D821(H) 16GB
bitdomo said:
You have "remote: flash write failure" error. It means your emmc (internal storage) is broken and you cannot modify the data on it. You have to rma your device.
Just for matter of research can you enter to fastboot and post the variable line here?
Mine is: hammerhead D821(H) 16GB
Click to expand...
Click to collapse
Sorry I meant to tell you yesterday... D820H 16GB. Should I still be able to toggle the tamper tag so they will take it back with no problems? Or am I screwed?
aburn95 said:
Sorry I meant to tell you yesterday... 820H. Should I still be able to toggle the tamper so they will take it back with no problems? Or am I screwed?
Click to expand...
Click to collapse
You should be able to if you managed to lock the bootloader. The name of the zip does not came into my mind which you have to flash, but you have to do it with the adb sideload command because you cant copy anything to your phone, or use adb push command to push it to the "/" folder because it is mounted to the ram which you can write not like your storage . If you bought your phone from google it does not matter you have tamper flag set to 1.
bitdomo said:
You should be able to if you managed to lock the bootloader. The name of the zip does not came into my mind which you have to flash, but you have to do it with the adb sideload command because you cant copy anything to your phone, or use adb push command to push it to the "/" folder because it is mounted to the ram which you can write not like your storage . If you bought your phone from google it does not matter you have tamper flag set to 1.
Click to expand...
Click to collapse
Ok thanks. I haven't quite figured out the adb sideload function yet. I tried doing it through TWRP but it just sits there and does nothing after selecting. Maybe I'm trying the wrong thing. I got my phone from T-Mobile so I'll need to solve this. Thanks for the help.
This phone is being a real a-hole. I'm trying to boot to stock recovery but it just sits on a screen with a really big android with wiggling antennae. I pressed up+power many times but it stayed that way. So I tried booting to TWRP again and it did but went immediately to an "OpenRecoveryScript," had a little bar at the bottom for a while with some other stuff on the screen, then turned off.
I tried stock recovery again and it went to the little dead android this time but still nothing when I press up+power.

HTC One S C2 Help Please

Hi, i want to install Cyanogenmod 10.2 to my phone, but i did wrong. Now my phone doesn't power up. i can enter bootloader mode, there isn't a problem with it. what can i do now please help...
And there is my bootloader screen.
Now i relocked. i'll try to install original ruu.
help please, i can't find acceptable Ruu for my version
I'd suggest starting from the beginning by going into fastboot mode and wiping system and boot and then fastboot flash the CM boot.img and recovery.img. If you can get into a recovery then you should be able to mount USB storage, push across a zip for CM10 that will work and then flash it.
Sent from my D6503 using XDA Free mobile app
omg_penguin said:
I'd suggest starting from the beginning by going into fastboot mode and wiping system and boot and then fastboot flash the CM boot.img and recovery.img. If you can get into a recovery then you should be able to mount USB storage, push across a zip for CM10 that will work and then flash it.
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for answer!
Unfortunately there isn't any CM file in my phone and i don't enter flashing, wiping system or anything else... i only see my bootloader screen. My phone only restarting. i think there is only way. i relocked it and i trying find suitable Ruu. :/
SinanJan said:
Thanks for answer!
Unfortunately there isn't any CM file in my phone and i don't enter flashing, wiping system or anything else... i only see my bootloader screen. My phone only restarting. i think there is only way. i relocked it and i trying find suitable Ruu. :/
Click to expand...
Click to collapse
When I soft-bricked mine, I couldn't find any RUU that would work, so I just thought I'd try and give you a different route. You should be able to get into fastboot mode if you can get into the bootloader? If you unlock the bootloader again, you can cycle through the bootloader options with the volume keys and select with the power button. If you select fastboot, or see "fastboot" highlighted, you can connect the phone to your computer and issue fastboot commands. If you've never done that before, I could give you a quick tutorial on how to, as I know it will definitely work whilst RUU's can be hard to find... Good luck though!!
omg_penguin said:
When I soft-bricked mine, I couldn't find any RUU that would work, so I just thought I'd try and give you a different route. You should be able to get into fastboot mode if you can get into the bootloader? If you unlock the bootloader again, you can cycle through the bootloader options with the volume keys and select with the power button. If you select fastboot, or see "fastboot" highlighted, you can connect the phone to your computer and issue fastboot commands. If you've never done that before, I could give you a quick tutorial on how to, as I know it will definitely work whilst RUU's can be hard to find... Good luck though!!
Click to expand...
Click to collapse
i really need help when i unlock the bootloader again, what's the next move? i haven't installed rom before from computer.
i solved my problem :good::good:

Can't boot into recovery. any idea if this can be fixed?

I tried to root my Opo, but it started to go wrong after i flashed it. It went to reboot into TWRP, but all that happened was it crashed. the 1+ logo comes on and then the screen goes blank. This Happens all the time when I try a "fastboot oem unlock", factory reset, or a boot recovery.. the fastboot does work, but the device is also locked and i can't do a recovery due to this. I tried to do the root tutorial on youtube by C4ETech.. help please!
@nickizm, when you boot to fastboot and enter the command "fastboot devices", can you see your device listed on the screen?
Thanks for the reply.. The fastboot work fines apart from when I try to unlock the devices and it reboots into recovery, it crashes and doesn't unlock.. the rest of the phone works fine apart from the recovery... my bootloader is also locked and I can't unlock it due to crashing
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screem enabled: false
I can't be certain but I'm pretty sure I read a similar issue to this a few days ago that was caused by not having the latest fastboot software, the user resolved it by downloading the latest android sdk and trying again.
Worth a shot.
Hope it helps.
Powered by Bacon
I had trouble when I first tried to root. Twrp wouldn't install. I ran some command which loaded it up but didn't install it on the phone, I was the able to root my phone.
Make sure you have latest oneplus one drivers. Have you tried using oneplus one toolkit to install recovery?
Sent from my Oneplus One using XDA Free mobile app.
I've tried to install a recovery, but my device is locked. If i do a "fastboot oem unlock" is just crashes on me when it going into recovery. I also get the same crash when I do a factory data reset or if I reboot into recovery. I think it's definitely something to do with the recovery, but since my device is locked i'm not sure what to do?... cheers again
nickizm said:
I've tried to install a recovery, but my device is locked. If i do a "fastboot oem unlock" is just crashes on me when it going into recovery. I also get the same crash when I do a factory data reset or if I reboot into recovery. I think it's definitely something to do with the recovery, but since my device is locked i'm not sure what to do?... cheers again
Click to expand...
Click to collapse
Did you try with the latest android sdk?
Powered by Bacon
I'm sure I did.. It wasn't that old.. I can try again, but the problem is I won't be able to unlock my phone??
is this the right link? http://developer.android.com/sdk/installing/index.html?pkg=studio
New drivers, exactly the same
Have you tried using a toolkit to do the unlock for you? People usually advise against using toolkits to do it for you as it prevents you gaining the experience of doing it yourself, but since it's not working when doing it yourself I don't see any harm in trying a toolkit.
You can find several options at the bottom of @timmaaa's resources roll-up thread here
Rkr87 said:
Have you tried using a toolkit to do the unlock for you? People usually advise against using toolkits to do it for you as it prevents you gaining the experience of doing it yourself, but since it's not working when doing it yourself I don't see any harm in trying a toolkit.
You can find several options at the bottom of @timmaaa's resources roll-up thread here
Click to expand...
Click to collapse
Yea i have also tried the tool kit V2
My problem is that the recovery is damaged in some way and my device is locked. i can't "fastboot oem unlock" as it just crashes when it goes to reboot.. is there a way to unlock my device with another method or can the recovery be repaired some how? i'm such noob
patstar5 said:
I had trouble when I first tried to root. Twrp wouldn't install. I ran some command which loaded it up but didn't install it on the phone, I was the able to root my phone.
Make sure you have latest oneplus one drivers. Have you tried using oneplus one toolkit to install recovery?
Sent from my Oneplus One using XDA Free mobile app.
Click to expand...
Click to collapse
Ye i tried that as well.. can't unlock the device as it just crashes when it goes to reboot into recovery
I think you might be out of luck, unless someone here more knowledgeable than I can help.
If you have a recovery image (not zip) you can try running the following command (make sure the img file is in the same directory as your adb/fastboot files and rename it "recovery");
Code:
fastboot boot recovery.img
What this allows you to do is boot into the TWRP recovery without having it installed on your phone, but I think I read somewhere that this command no longer works.
EDIT: If the above command will let you boot into TWRP, you'll want to read the guide here and flash the script.
Rkr87 said:
I think you might be out of luck, unless someone here more knowledgeable than I can help.
If you have a recovery image (not zip) you can try running the following command (make sure the img file is in the same directory as your adb/fastboot files and rename it "recovery");
Code:
fastboot boot recovery.img
What this allows you to do is boot into the TWRP recovery without having it installed on your phone, but I think I read somewhere that this command no longer works.
EDIT: If the above command will let you boot into TWRP, you'll want to read the guide here and flash the script.
Click to expand...
Click to collapse
I've tried that as well, but as my device is locked it won't allow it.. I'm stuck in limbo for now unless there is a way to unlock my device or repair the recovery? thanks for trying anyways
nickizm said:
I've tried that as well, but as my device is locked it won't allow it.. I'm stuck in limbo for now unless there is a way to unlock my device or repair the recovery? thanks for trying anyways
Click to expand...
Click to collapse
One last effort, after a bit of reading I've seen a few people with your issue have resolved it by flashing ColorOS (Chinese Stock ROM) and then going back to a custom rom once everything is fixed.
You can find a guide on how to do this here
Rkr87 said:
One last effort, after a bit of reading I've seen a few people with your issue have resolved it by flashing ColorOS (Chinese Stock ROM) and then going back to a custom rom once everything is fixed.
You can find a guide on how to do this here
Click to expand...
Click to collapse
Cheers mate! I just had a quick flick through it and it looks promising? the only problem seems to be with drivers in windows 7 which i am also using.. I'll see if I can do it via linux or i'll have to install xp on my old laptop or something.. I'll save this for tomorrow tho as it's late and will let you know how I get on with it. thanks for the help
nickizm said:
Cheers mate! I just had a quick flick through it and it looks promising? the only problem seems to be with drivers in windows 7 which i am also using.. I'll see if I can do it via linux or i'll have to install xp on my old laptop or something.. I'll save this for tomorrow tho as it's late and will let you know how I get on with it. thanks for the help
Click to expand...
Click to collapse
No worries! Let me know how it goes good luck!
Rkr87 said:
No worries! Let me know how it goes good luck!
Click to expand...
Click to collapse
Definitely! cheers again
nickizm said:
I tried to root my Opo, but it started to go wrong after i flashed it. It went to reboot into TWRP, but all that happened was it crashed. the 1+ logo comes on and then the screen goes blank. This Happens all the time when I try a "fastboot oem unlock", factory reset, or a boot recovery.. the fastboot does work, but the device is also locked and i can't do a recovery due to this. I tried to do the root tutorial on youtube by C4ETech.. help please!
Click to expand...
Click to collapse
can you give a little detail about
"device is also locked and i can't do a recovery due to this"
you did fastboot oem unlock. so saved data is wiped. but you should be able to boot into android system,
if so, enable "developer options" by clicking "settings" --> "about phone" --> "Build Number" click it 7 times,
then go into settings developer options and enable USB debugging.
then, use not fastboot, but adb to boot into recovery.
adb reboot recovery
Click to expand...
Click to collapse
there you can got into recovery.
Gh05tShie1d said:
can you give a little detail about
"device is also locked and i can't do a recovery due to this"
you did fastboot oem unlock. so saved data is wiped. but you should be able to boot into android system,
if so, enable "developer options" by clicking "settings" --> "about phone" --> "Build Number" click it 7 times,
then go into settings developer options and enable USB debugging.
then, use not fastboot, but adb to boot into recovery.
there you can got into recovery.
Click to expand...
Click to collapse
That doesn't work as my device crashes when it goes into recovery..
eg: "fastboot oem unlock", factory reset, or a boot recovery all crash as my recovery isn't working. When my device goes to reboot in recovery the 1+ logo comes up, fades out to like a blueish from the white 1+ logo and crashes.. so basically it's looked and I can't get into recovery.. thanks for trying

Categories

Resources