Today I managed to succesfully root my device. Then I wanted the 2.3.4 update so I did that following this guide (I have i9023 GRI54, KB3). Now comes the strange part: my Android-version is indeed 2.3.4, but my Smallband version is I9023XXKD1 now. And my Build-number has changed to GRJ22. Is this normal?
Anyway, then I flashed CWM again, because I lost root. I don't know what went wrong, but when I'm trying to get into recovery mode, it shows a exclamation mark in a triangle together with a small droid. I can't turn off my phone, so I can only get away from that screen by pulling out the battery.
I flashed CWM exactly the same as I did before the update to 2.3.4, 2 hours ago. Then it all went perfectly fine. What did I do wrong??
Maybe I need the i9020 version of CWM now? According to the bootloader interface my version is i9020. But it also said that before the 2.3.4 update.
Ok, now I managed to get root back. According to Rom Manager I have CWM installed, but I can't access it with bootloader interface.
And my phone also doesn't recognise my "sd-card" anymore.... That's probably the reason why I can't access recovery mode (it goes into normal recovery mode, not CWM)? If I flash CWM again, there is no error message, but it still doesn't work. I can't go back to stock because I need CWM for that!
Related
Okay here are my problems:
I'm running a Nexus S - Rogers version (i9020AUCKE1)
My goal is to get to 2.3.6.
I can't connect via the USB anymore, whenever I try Windows says that it doesn't recognize the USB device. Mac doesn't say anything at all. I have tried turning USB debugging on (though I didn't before and it worked previously) - and I've tried multiple cables.
I can't install / update anything I've found so far through the recovery - everything I've tried fails signature validation.
I'm currently running this version:
Android 2.3.4/GTJ61/UCKE1 Radio/KA3 Bootloader
Unofficial, unsigned, must flash through ClockworkMod Recovery. Contains recovery, radio and bootloader.
Courtesy of XDA forum member scott8281
My phone is unlocked and was previously rooted; though through a series of unfortunate events, I no longer have superuser access directly on the phone (though there is a superuser.zip on my sdcard) and I'm on stock recovery instead of clockwork.
What I'm hopeful to do, at this point, is to get super user access again, get Clockwork back on it and skip the signature validation so I can get it updated. But I haven't figured out a way to do it yet.
I tried z4root but when I tried to root it, the app started but closed itself after about 2 minutes and didn't seem to actually do anything.
Anyone have any ideas of what I can try?
update - I've tried Gingerbreak and it's just hanging on me - doesn't seem to work for either.
Also - I can't find the USB Settings anywhere. I'm wondering if that's my problem with the ROM - it doesn't have the proper USB settings.
Hi,
I got a similiar problem a few weeks ago and found a solution in the internet, that worked for me: Just shut down the phone, put the battery out for approx. a minute. Put it back in and boot, and try again.
I could not believe it, because I don't see the technical explaniation how this could solve this problem - but it did worked, and that is what counts.
Good luck
If your phone is unlocked download rom manager and flash cwm from the app. Do this just after a fresh boot of the phone. If cwm isn't there when you boot into recovery reboot the phone and again flash cwm from rom manager as soon as the phone boots. This time it should stick. From cwm flash superuser.zip and you are rooted again. Then just flash the rooted version of the update.
Normally I recommend flashing recovery from fastboot, but in your case rom manager is the only way to go.
Sent from my Nexus S 4G using xda premium
Long story short, I may have bricked my phone trying to update to 4.0.3
I have a Nexus S (GSM) with a Telus SIM
I used ROM Manager to flash the stock 2.3.3 then upgraded to 2.3.6 so I could flash the 4.0.3 update, but now my phone apparently isn't rooted anymore but is still unlocked, as I have the unlocked icon when I boot.
I can't even connect to the Telus network at the moment. Any help available? I'm a bit lost here.
Thanks.
B.
I flashed the OTA on my i9023 from 2.3.6. All ok until reboot, for now my phone don't boot, it seems dead.
rottencrab said:
Long story short, I may have bricked my phone trying to update to 4.0.3
I have a Nexus S (GSM) with a Telus SIM
I used ROM Manager to flash the stock 2.3.3 then upgraded to 2.3.6 so I could flash the 4.0.3 update, but now my phone apparently isn't rooted anymore but is still unlocked, as I have the unlocked icon when I boot.
I can't even connect to the Telus network at the moment. Any help available? I'm a bit lost here.
Thanks.
B.
Click to expand...
Click to collapse
Format /system, then flash 2.3.6 full ROM. Start from there again.
tisi1988 said:
I flashed the OTA on my i9023 from 2.3.6. All ok until reboot, for now my phone don't boot, it seems dead.
Click to expand...
Click to collapse
Describe "don't boot" better. What exactly do you see? Stuck at some screen? Totally black/nothing when pressing the power button?
Might not be alone
Hi, sounds like I'm in the same boat.
Fully details on my phone
Nexus S (of course), i9020T, running CM7 before the trouble started. In order to load the OTA update I tried to flash back to stock 2.3.6. Flashed to 2.3.6, went successful (quickly went through setup process on 2.3.6, just to check.)
Then went back onto clockwork mod to install the ICS update. update went very quickly and I then tried rebooting the phone. Just get the ICS boot screen on an endless loop. Start the phone in fastboot mode, but now can't launch recovery. Device doesn't show up when connected with USB on Mac OR Windows. Ran ADB on computer and it says the device is not connected. USB drivers cannot be installed for the device.
When I try to boot into recovery and I get the "dead android" image (laying on its back with a red exclamation mark over it)
As with using ADB, tried using Unbrickable app on my linux box. No luck, says device not found. No computer can "see" my nexus S, even though it can draw a charge from USB and it shows up as "android 1.0" if I connect to a Windows machine.
telus nexus s is i9020A, and im pretty sure that update was for i9020T and i9023 nexus s only.
This morning my phone (nexus S) told me it had an update to 4.0.4, which i tapped install. I previously had ICS 4.0 (i think).
When the phone boots up all i get is the flashing colourful spash screen, and it doesn't move on from there.
I tried to get into recovery mode, but all i get is a android man lying down with an exclamation mark over him.
What can i do? what commands for ADB do i need to revert it back to a functional state? I hope its not bricked :-{
Was your phone rooted?
Sent from my GT-I9100 using XDA
rooted
Im not sure what the defination of rooted is but i previously had cyanogen mod on, but reverted back to standard android 2.3 then to the standard android 4, which when installed seem to also remove CWM which i had on.
It is unlocked though
it may work
I will suggest you either you can go to Samsung service center as your phone warranty is not void or nigher you have done anything that is not supported by Samsung or 2nd solution is that download the suitable official ROM from this forum for your phone, and also ODIN, and flash it by going into download mode.
also i will suggest you gain some knowledge how to flash your phone with ODIN before flashing it.
Sounds like you bricked it to me... good luck!!
jackwoz said:
This morning my phone (nexus S) told me it had an update to 4.0.4, which i tapped install. I previously had ICS 4.0 (i think).
When the phone boots up all i get is the flashing colourful spash screen, and it doesn't move on from there.
I tried to get into recovery mode, but all i get is a android man lying down with an exclamation mark over him.
What can i do? what commands for ADB do i need to revert it back to a functional state? I hope its not bricked :-{
Click to expand...
Click to collapse
pull the battery out..and try to enter recovery mod and wipe data/factory resert
Brick or no brick
Hi,
In order to find out if your phone is bricked you need to first remove the battery, replace it and then the do the three key boot to get the phone to boot into download mode.
If that works then you can locate the right firmware and then install via Odin.
If not the next step is to get a jig that forces the phone into download mode (provided it still has bootloaders) and then via Odin again install your firmware.
Otherwise it's a trip to Samsung I think.
Try pulling the battery and wait a few minutes, insert battery and try entering recovery mode again.
Hi.
Been trying for a week to get phone back online, it's time to ask for help. If it seems like a did something stupid it's because I did, been "learning" as I go.
Phone is Huawei Honor, european edition. Was delivered with Norwegian ICS 4.0.3 B925 firmware without access to pink screen.
I wanted to root it so I ended up downgrading to stock firmware B886 2.3.6 via phone menu. Now I could access pink screen / recovery.
I replaced recovery.img with CWM 5.0.2.7 and installed su (rooted the phone). All well.
Now I wanted to get ICS somehow. Tried installing many different ROMs via menu and pink screen, no process started. Google says 2.3.6 is a ROM not capable of being flashed over. In a rather impulsive moment I wiped the phone (data/cache/dalvik). Tried putting different ROMs in dload on internal/external sd card. Tried menu and pink screen again, no go.
Ended up flashing MIUI 2.12.14. Major mistake I think.
Status: Boot(loop?) to golden MIUI/Xiaomi.com logo, nothing happens. I can access CWM so not bricked?
My goal is rooted ICS, but at this stage I take anything. Im travelling rather far in few days (visiting family for Christmas) and NEED a working phone.
ANY/all help greatly appreciated.
Is there perhaps a way to flash stock rom's from pc?
Trying to revert to stock now, wiped data/cache/dalvik and placed B870 rom i sdcard/dload (again). Volume+/- +power takes me to pink screen with usb access, no upgrade happening. Same with B925. But:
Tried replacing recovery.img in case stock rom needs stock recovery, but cwm still loads??
EDIT::In addition (after wipe), MIUI logo is still there..what have I not wiped? If i format /recovery I suspect I might not be able to reach my device in any way..correct? Please advice
happyhd said:
Trying to revert to stock now, wiped data/cache/dalvik and placed B870 rom i sdcard/dload (again). Volume+/- +power takes me to pink screen with usb access, no upgrade happening. Same with B925. But:
Tried replacing recovery.img in case stock rom needs stock recovery, but cwm still loads??
EDIT::In addition (after wipe), MIUI logo is still there..what have I not wiped? If i format /recovery I suspect I might not be able to reach my device in any way..correct? Please advice
Click to expand...
Click to collapse
Can this be kernel-related? If so, is there a two-part process to follow for a custom ROM ? First flash kernel, then ROM?
bump
EDIT::after trying mekoo os (nice but hung) even cwm started acting up, hanging and didnt find usb / sd card no more. Removed sd card and put B925 on internal sd card in dload-folder. Removed battery and started with usb-cable + volume up/down NOT power button: Upgraydd.
Now for a 2nd, more cautious attempt at root.
happyhd said:
Ended up flashing MIUI 2.12.14. Major mistake I think.
Click to expand...
Click to collapse
I have also flashed MIUI and manu things doesn't work for me for instance the browser. I have tried different browsers but still not satisfied, because when browsing I suddenly return to home screen. Now I want to get back to stock rom B925 from MIUI. Any advice before I start the process?
morsoe said:
I have also flashed MIUI and manu things doesn't work for me for instance the browser. I have tried different browsers but still not satisfied, because when browsing I suddenly return to home screen. Now I want to get back to stock rom B925 from MIUI. Any advice before I start the process?
Click to expand...
Click to collapse
Well, I tried and failed alot. Try having the stock B925 in a dload folder on the internal card AND remove external sdcard if you have it.
happyhd said:
Hi.
Been trying for a week to get phone back online, it's time to ask for help. If it seems like a did something stupid it's because I did, been "learning" as I go.
Phone is Huawei Honor, european edition. Was delivered with Norwegian ICS 4.0.3 B925 firmware without access to pink screen.
I wanted to root it so I ended up downgrading to stock firmware B886 2.3.6 via phone menu. Now I could access pink screen / recovery.
I replaced recovery.img with CWM 5.0.2.7 and installed su (rooted the phone). All well.
Now I wanted to get ICS somehow. Tried installing many different ROMs via menu and pink screen, no process started. Google says 2.3.6 is a ROM not capable of being flashed over. In a rather impulsive moment I wiped the phone (data/cache/dalvik). Tried putting different ROMs in dload on internal/external sd card. Tried menu and pink screen again, no go.
Ended up flashing MIUI 2.12.14. Major mistake I think.
Status: Boot(loop?) to golden MIUI/Xiaomi.com logo, nothing happens. I can access CWM so not bricked?
My goal is rooted ICS, but at this stage I take anything. Im travelling rather far in few days (visiting family for Christmas) and NEED a working phone.
ANY/all help greatly appreciated.
Click to expand...
Click to collapse
Normally if you just put the dload folder of the B925 rom on your SD card, and then boot with power and +- volume buttons without the usb cable in, it will automatically install the firmware.
hope it helped!
My son was trying to unlock his Verizon Galaxy S3 and install Cyanogen Mod (KitKat). I didn't supervise, so I only have what he told me:
https://www.youtube.com/watch?v=AQdSOTdV06Q
I followed this guy's instructions to the T, but I forgot to unlock the bootloader for the phone, which the guy never mentions. He just assumes that you know that you have to have your phone rooted and the bootloader unlocked so you can flash a custom os to the phone's kernel. I flashed the image, and then put it into recovery mode, and it came up with the big yellow triangle with the message "THIS PHONE HAS SOFTWARE ON IT THAT IS NOT AUTHORIZED BY VERIZON WIRELESS!!!" I reset the phone by plugging it into my computer, and then tried to unlock the bootloader with an app and reboot and flash the image again. After i restarted the phone to put it into recovery mode, it wouldn't turn on.
I made an attempt to fix it, using the post on this board: http://forum.xda-developers.com/showthread.php?t=2581166 and got to a point where it would boot off of the microSD. I then tried to get it back to stock, so we could start all over again but wound up back to where it will now boot, but goes directly to the "THIS PHONE HAS SOFTWARE ON IT THAT IS NOT AUTHORIZED..." and I can't seem to get past this point.
Thanks for any help you can provide. He is currently stuck using a Galaxy S that I was able to put Cyanogen Mod on, so it's not as bad as it could have been!
Rob
rallen911 said:
My son was trying to unlock his Verizon Galaxy S3 and install Cyanogen Mod (KitKat). I didn't supervise, so I only have what he told me:
https://www.youtube.com/watch?v=AQdSOTdV06Q
I followed this guy's instructions to the T, but I forgot to unlock the bootloader for the phone, which the guy never mentions. He just assumes that you know that you have to have your phone rooted and the bootloader unlocked so you can flash a custom os to the phone's kernel. I flashed the image, and then put it into recovery mode, and it came up with the big yellow triangle with the message "THIS PHONE HAS SOFTWARE ON IT THAT IS NOT AUTHORIZED BY VERIZON WIRELESS!!!" I reset the phone by plugging it into my computer, and then tried to unlock the bootloader with an app and reboot and flash the image again. After i restarted the phone to put it into recovery mode, it wouldn't turn on.
I made an attempt to fix it, using the post on this board: http://forum.xda-developers.com/showthread.php?t=2581166 and got to a point where it would boot off of the microSD. I then tried to get it back to stock, so we could start all over again but wound up back to where it will now boot, but goes directly to the "THIS PHONE HAS SOFTWARE ON IT THAT IS NOT AUTHORIZED..." and I can't seem to get past this point.
Thanks for any help you can provide. He is currently stuck using a Galaxy S that I was able to put Cyanogen Mod on, so it's not as bad as it could have been!
Rob
Click to expand...
Click to collapse
Go to download mod (volume down + home + power button) then flash stock 4.3 or 4.4.2 via odin the one you was on.
To add to the above reply. If you are on 4.3 or 4.4.2 stock bootloader, you cannot unlock it to install custom recovery and custom ROM. You are limited to safestrap and compatible (same OS version, 4.3 or 4.4.2) touchwiz ROMs only. Do not attempt to use the app to unlock your phone once you are back on stock or you will brick again.