Hi experts,
today I was very successfull in breaking my Nexus S.
- It is a European Nexus S (i9023?)
- It was running Cyanogenmod 10.1
- I tried to wipe it completely before going for 10.2
- To do so I used Nexus Root Toolkit for the 1st time
- TWRP recovery was running and used to wipe things (maybe to many...)
- Something went obviously wrong (my fault) :crying:
Now:
- Power button not working (battery needs to be removed for power off)
- It boots only till the Google logo is shown together with the open lock symbol
- It seems to be frozen then
- Nexus Root Toolkit is not able to connect to the phone anymore (adb/fastboot)
To prevent any further collateral damage, I am now open for suggestions about how to proceed.
All I want is to have it back up and running, no matter which system.
Thank you,
B
Can you reach Bootloader menu and then try reaching your phone with fastboot? (power and volume up when phone is switched off)
If yes, get Image here (developers . google . com / android / nexus / images) /sorry cannot post links -.-
And then
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
fastboot -w update image-soju-jzo54k.zip
Related
I broke my xperia l lcd last year. Digitizer was partly working. Developer option was not enabled.
Recently I found this thead and started playing:-
1. No display, so could not use a graphical recovery to flash a rom (with debug opt enabled).
2. Flashed Kitkat Omni rom (it has system.img, boot.img...) using fastboot.
3. Now I can use [email protected] and other similar tools to use the phone somewhat.
My problems / queries:-
1. Main problem I do not have app level root access, tried various methods but failed.
2. Cannot flash recovery image (using fastboot / flash_image) to use philz / cwm.. It says remote command not allowed / write not permitted. When I flashed the philz recovery as boot the omni rom does not start. Any other options?
3. Can some one let me know how to create a shortcut for system menu app 'Cast Screen' (with predefined display device) in desktop / or put it in autostart.
I leaned a lot due to this broken phone. Thanks xda, Omni Rom & [email protected] developers. k.janku1 , many others and of-course Sony mobile.
AD.
At last I found a solution for rooting
I have philz touch in my other phone. I noticed it was very easy to use blindly as it has touch feedback.
So I got the root problem solved by following steps:-
Enter fastboot mode [switch off phone - press vol up + usb cable insert -> blue light will turn on]
fastboot -w
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot philz_touch.img [temporarily, as omni will not boot with philz_cwm]
fastboot reboot
while starting pink light is on press vol down to enter recovery mode [philz touch]
Touch buttons below
down = up = back = enter
press back several times to reset the cursor at top
down once (intsall from zip) -> press power button
down 4 times (as it has internal sd and ext sd, install from side laod) -> press power button
adb sideload Update_SuperSU.zip
wait
adb reboot bootloader [fastboot mode ]
fastboot flash boot boot.img [omni's original boot.img]
fastboot reboot
Now as I got the root power every other problem will be solved very soon.
Hope this will help someone someday.
Hey guys, so I have this dilemma on my hands. One of my friends has a Nexus 5 that has a power button issue. It seemed like a stuck power button, because even cleaning it did not solve the issue. So I removed the power button, and it finally turned on. However, it's now stuck in a Google logo bootloop.
The Objective:
To recover all data on the device. This is a must.
The Obstacles:
- No physical power button, but I can place a pair of tweezers on the terminals on the board to simulate a power button press.
- Bootloader is locked (I can unlock it, but that erases all data on the phone).
- Cannot enter proper stock recovery (I get a "no command" error when I do; I've tried all button combinations afterwards, including the ones from HERE, but to no avail).
- USB debugging was not enabled on the phone when booting normally, so even though the phone is recognized by my PC, I cannot do anything using ADB.
- Fastboot mode is the only successful mode I can reach on the phone.
The Final Question:
Does anyone know how I can successfully recover all the data on the phone using ADB or any other method, having the above obstacles?
Thanks in advance.
If you can reach fastboot without any problem, you can try to boot a custom recovery image using the following command : fastboot boot recovery yourcustomrecovery.img
(if you dont have a custom recovery, you need to flash one with : fastboot flash recovery yourcustomrecovery.img)
It will boot in recovery mode and, I hope, allow you to have an adb access and recover your data.
edit : since your bootloader is locked, i guess this won't work.
MrKhozam said:
Hey guys, so I have this dilemma on my hands. One of my friends has a Nexus 5 that has a power button issue. It seemed like a stuck power button, because even cleaning it did not solve the issue. So I removed the power button, and it finally turned on. However, it's now stuck in a Google logo bootloop.
The Objective:
To recover all data on the device. This is a must.
The Obstacles:
- No physical power button, but I can place a pair of tweezers on the terminals on the board to simulate a power button press.
- Bootloader is locked (I can unlock it, but that erases all data on the phone).
- Cannot enter proper stock recovery (I get a "no command" error when I do; I've tried all button combinations afterwards, including the ones from HERE, but to no avail).
- USB debugging was not enabled on the phone when booting normally, so even though the phone is recognized by my PC, I cannot do anything using ADB.
- Fastboot mode is the only successful mode I can reach on the phone.
The Final Question:
Does anyone know how I can successfully recover all the data on the phone using ADB or any other method, having the above obstacles?
Thanks in advance.
Click to expand...
Click to collapse
I bit of a trick. Try 'fastboot flash boot recovery.img' but instead of kernel flash twrp. After flash do a 'fastboot reboot'. It will boot recovery. Via twrp the pc will recognize phone as a media storage. You will not erase any data
icrunchbanger said:
I bit of a trick. Try 'fastboot flash boot recovery.img' but instead of kernel flash twrp. After flash do a 'fastboot reboot'. It will boot recovery. Via twrp the pc will recognize phone as a media storage. You will not erase any data
Click to expand...
Click to collapse
Thanks for the response, but the bootloader has to be unlocked for that to work, and while I can do that, it will wipe the data I need.
Hello,
as the title says... I bricked my phone. In the past, I successfully installed LineageOS on my old Galaxy S3. I got a used Huawei P9 Lite recently and wanted to install a custom ROM. Here's what happened:
1. Unlocked the phone
2. Accessed Fastboot mode
3. Installed TWRP* via fastboot flash recovery file.img
4. This didn't work and I read on the web, I could try to flash revocery2 with fastboot flash recovery2 file.img
5. This didn't help either, so I decided to cancel my plan and use the manufactorer's system since the system still booted (of course, I didn't install any custom OS).
6. The phone told me on each startup it's unlocked. I didn't need the unlock anymore, so I accessed the Fastboot mode again.
7. I re-locked the system by using fastboot oem relock password.
8. The phone asked me to do confirm this action and do a factory reset
9. After this, I'm stuck at the Huawei logo and can't access Fastboot mode anymore!
When I shut down the phone, it immediately restarts itself. No chance to get into Fastboot mode again, which I did through pressing Vol- and plugging in an USB cable.
*I tried several versions, 3.0.1 and 3.2.1 since no version worked
This may be a beginner's fault, my last phone was already unlocked and I had not a single problem back then. But this time... I hope you can help me.
What would happen if I let drain the battery down to 0% - the phone wouldn't restart of course. If I press Vol- and plug it in, would I come back to Fastboot mode or would it stay in this loop?
Any help is appreciated!
Hello guys, today I updated my phone to Android 10 and it "bricked" I guess. So I found a fix, which is very simple. For the *s read at the bottom of the thread, enjoy.
STEPS:
1) Set your phone in Fastboot mode and plug it into your PC
2) Open a terminal tab in your PC and type these commands:
First:
Code:
fastboot getvar current-slot
Result will be:
Code:
current-slot: a [COLOR="Red"][B](or b)*[/B][/COLOR]
Second:
Code:
fastboot set_active a [COLOR="Red"][B](or b)*[/B][/COLOR]
After these steps, reboot your phone into recovery mode and do a factory reset and reboot again, then it should be fine. If you have any problem, let me know!
*if you have slot a as main, then the command will be
Code:
fastboot set_active a
Well, I guess you were not the one who found this out ?
A factory reset is also not nessesary, just flash V11, V10 or V09.
Cappucinto said:
Well, I guess you were not the one who found this out
A factory reset is also not nessesary, just flash V11, V10 or V09.
Click to expand...
Click to collapse
how please
i cant enter to recovery mode because of the bootloop even after hitting those comments
Cappucinto said:
Well, I guess you were not the one who found this out
A factory reset is also not nessesary, just flash V11, V10 or V09.
Click to expand...
Click to collapse
how if your bootloader is locked lol..
and yeah I found it out
Aragino said:
how if your bootloader is locked lol..
and yeah I found it out
Click to expand...
Click to collapse
did you solve it?the bootloader locked? can you help me how to unlock? i cant go through
my take on the FIX
1 - https://github.com/awake558/adb-win
2 - download/unpack run the commands from this folder.
3 - now put your phone in fastboot mode by holding power + volume down (-)
4 - now connect cable , now use the command - fastboot devices - you should get a serial number -
5 - use - fastboot getvar current-slot - it wil tell you if its on slot a or b now
6 - use - fastboot --set-active=b - or fastboot --set-active=a - or fastboot set_active other
7 - fastboot reboot - the phone will boot now and will ask for a code do nothing , just power off the phone -
8 - now turn on the phone by pressing power + volume up a screen with android robot will appear
9 - press power + volume up again and enter the recovery menu now using only volume up or down to navigate to reboot into system now select yes to confirm
10 - if reboot fails go back in to recovery and factory reset then reboot into system
after i got the greyscale screen, i flashed android 9 rom but the phone is stuck in another kind of bootloop,
was it the damaged partition or the working partition that i flashed the rom into?
can i still use those commands to unbrick my phone or i need to flash another rom ?
Does somebody of you succeded to update to Android 10 with OTA patch?
In affirmative case is there somebody who has the touch screen with double tap to wake like mine?
I still have the automatic updates disabled cause I'm scared about the phone brick in case it fails
I really don't know if Xiaomi will fix the upgrade issues that some Mi A2 Lite devices faced, like boot looping
Did you found some way to fix this? i flashed another rom so it keep with bootloop whatever i do
Not working with an unlocked bootloader here:
fastboot set_active b
Setting current slot to 'b'...
FAILED (remote: Slot Change is not allowed in Lock State
)
finished. total time: 0.000s
Hello people.
Until today I was using my Redmi 9 with MIUI 12 android 10 (lancelot_global_images_V12.0.4.0.QJCMIXM_20210331.0000.00_10.0_global_b92099d9f4) and I decided to upgrade to android 11 through fastboot (lancelot_global_images_V12.0.1.0.RJCMIXM_20210609.0000.00_11.0_global_0b17afb77b).
Everything went well, I installed android 11 and the device started normally. I turned off the device before doing the initial settings because I wanted to install TWRP (twrp-3.4.2b-0108-LR), so I did the same TWRP installation process as I did on android 10.
These were the commands I used:
1 - fastboot flash recovery twrp-3.4.2B-0108.img
2 - fastboot flash misc misc.bin
3 - fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
4 - fastboot boot twrp-3.4.2B-0108.img
After that, the device restarted but MIUI did not start again. "Redmi" appears on the screen for a few seconds then restarts again and again.
And now comes the real problem and also the reason for this post...
I cannot access recovery or fastboot mode!
I can't even turn off the device.
I can't do anything but wait for the battery to run out.
If I hold Power + VolumeUp = It keeps rebooting
If I hold Power + VolumeDown = It keeps rebooting
If I only hold Power = It keeps rebooting
If I hold all of them it stops rebooting and keeps the black screen as if it's off, but when I stop holding, the bootloop starts again.
I don't know what to do, I hope any of you can help me.
Thanks for the attention.
Re-flash STOCK ROM to get rid off of all the modifications you applied so far, or take it to authorized service center and let them fix it.
Check the links from this thread:
Phone Bricked
This seems informative:
Redmi Note 9 Bricked