I upgraded my Nexus S i9023 to ICS 4.0.3. Phone is not rooted or anything. I just followed to procedure given in this post. It works good for most stuff, but some apps seem to not work any more.
The problem is that I can now not enter recovery mode any more. When I power up phone and hold "volume up" button, I get bootloader screen. When I select "Recovery" from this screen, I get short image of android lying on back, with chest open. This image disappears after short time, and phone hangs.
Please help. How can I restore standard 2.3.6 without having to root phone phone or do other "non standard" stuff? I have spent a couple of hours searching this forum, and found many people reporting this problem, but no solution I (super NOOOB) can follow. Seems like all solutions are for "experienced hackers".
Cheers, David
simple solution: use flashlight
Hello, thanks for hint. I tried couple of different tourches before found one that I can sort of read displays. Shine light from bottom of phone, and displays is nearly readable.
- After display goes blank, shining light on displays shows android guy with warning triangle. Hold the power button and tap volume up. You'll see a menu with 4 items. Could not read text, but figured first item is "Reboot", and second "Apply update from /sdcard". I selected second item.
- Now with volume can scroll up and down through many items. Seems to be folders on sdcard. I placed only one file in root of sdcard = "2.3.3(GRI40)_to_2.3.6.zip". Problem is I could not find "4.0.3_to_2.3.6.zip". So tried what I have.
- As expected it failed. I am now trying to find a "4.0.3" to "2.3.6" incremental update. Will report if found.
Lying on his back with his chest open? It sounds like he has just had his heart plucked out in an Aztec Ceremony, or he is being prepared for Open Heart Surgery. Seriously, I've never seen that image.
There is no way to downgrade with stock recovery....
Sent from my ice cream powered Nexus S
try download the clockworkmod's recovery image and use fastboot:
fastboot boot (recovery's filename)
to boot into clockworkmod's recovery
Related
So I have an lg g2x originally running gingerbread 2.3.3 and I went through this procedure -> http://forum.xda-developers.com/showthread.php?t=1259852&highlight=linux+g2x+root
Everything seemed to work as described except that the phone now will not boot. I get to the LG screen but then the buttons just blink and shuts down and tries to boot again.
I must have missed a step somewhere, though I am not sure where that might have happened. In any case, I would like to get this working or, at the very least, get the phone back and working.
I am running linux and do *not* have access to windows at all.
Which LG screen are you getting? The static one or the one with a moving green bar underneath it? Can you still boot into Clockworkmod Recovery or was that a no go? You need to give more detailed information so people can figure out at what point in the boot process your phone is rebooting.
I get that initial booting LG screen with the face and the letters LG, there is no green bar. It sits in that screen for 15 or 20 seconds then attempts to reboot. Well, thats what I assume happens. The screen goes black, the buttons along the bottom flash and then after a few seconds that white LG screen comes back and it does it all again. It never gets past that and never into CWM. I can still put it in the flash mode that allows nvflash to connect and do its thing, but thats about it.
If you have successfully nvflashed cwm. Then you should be able to get into cwm by holding volume down+power until it goes to a blueish LG screen. Then flash a rooted rom from there.
That is the easiest/safest way of rooting a g2x. If you haven't done this you can Google "nvflash g2x Linux" and find guides on how to do it.
Sent from my LG-P999 using xda premium
Right, thats exactly what should happen. Unfortunately, its not what actually happens. During bootup I a can hold power + volume down all day long and get the exact same behavior. Its a bit disconcerting.
[solved]
Guys, I found the problem and figured I would post it here for future folks.
I was unable to start my phone plugged into the charge (both to the computer and to the wall). I had to have the battery in for this to get to a good place. I guess initial startup just took too much power.
So if you do this, after using the restore script. Press the power button and volume down hold both, then *put in the battery*. Thats what worked for me.
thanks!
Howdy Folks.
Here is where i am with my Gtab experience. Reviewed the dummies site a few times...guess i am dumber than dumb when it comes to this stuff.
I have been on stock 1.1 3588 since day one. All i have ever been able to do was load CWM - which ended up not helping becuase now over a year later Viewsonic finally releases an OTA update - which does not work for me since i have CWM.
So i wanted to either get to 1.2 or at least back to stock w/out CWM so i can use the OTA update.
In the process of trying to load/flash something i got stuck on teh birds screen. Unable to boot up or go into CWM. Read the code reads on the dummies site and waited for battery drain. Today i try again and press power while holding + to get into CWM - Still get message: Detect a recovery key pressed Booting recovery image - NOTHING at all so battery drain did not work.
Look obviously a year later and i've got zero use out of this tablet, so it's never gonna happen for me.
If anyone lives in teh south Florida, WPB area and is willing to help - let me know. If someone is willing to help and i can ship this to them - almost as good.
I would like to get ICS loaded on this so i can use it, or stock loaded back so it can be sold. I paid over $300 so hate the idea of the waste but whatver im not techy at all and i guess this is just over me abilities - sucks to admit but i have spent hours.
Let me know. Thanks
Hendge said:
Howdy Folks.
Here is where i am with my Gtab experience. Reviewed the dummies site a few times...guess i am dumber than dumb when it comes to this stuff.
I have been on stock 1.1 3588 since day one. All i have ever been able to do was load CWM - which ended up not helping becuase now over a year later Viewsonic finally releases an OTA update - which does not work for me since i have CWM.
So i wanted to either get to 1.2 or at least back to stock w/out CWM so i can use the OTA update.
In the process of trying to load/flash something i got stuck on teh birds screen. Unable to boot up or go into CWM. Read the code reads on the dummies site and waited for battery drain. Today i try again and press power while holding + to get into CWM - Still get message: Detect a recovery key pressed Booting recovery image - NOTHING at all so battery drain did not work.
Look obviously a year later and i've got zero use out of this tablet, so it's never gonna happen for me.
If anyone lives in teh south Florida, WPB area and is willing to help - let me know. If someone is willing to help and i can ship this to them - almost as good.
I would like to get ICS loaded on this so i can use it, or stock loaded back so it can be sold. I paid over $300 so hate the idea of the waste but whatver im not techy at all and i guess this is just over me abilities - sucks to admit but i have spent hours.
Let me know. Thanks
Click to expand...
Click to collapse
Firstly this should not be too bad of an issue for you. Download this file http://www.mediafire.com/?0rgkcd0k4v30z4u
and connect your tablet in APX mode making sure the APX drivers are installed. Then just run the .bat file and watch the magic happen. It should let you boot back to 1.2 stock without much issue. If this does not work or you need more help just reply back. Someone should be able to help out.
I have found that you can pretty much self tutor through youtube. Search for the earliest gtab links. You can learn everything you need to know with step by step instructions. I knew nothing at first but have updated my gtab with every rom from gingerbread to the current ICS over the months. Give it a try, you be surprise how easy it is to do. All credit goes to the fine devs and experts on this site for making it so.
@Hendge..... I live in Vero Beach..... If all else you try fails and you have nothing else to try and you are out of options then PM me in this forum. I should be able to copy some of my "fixit tools" programs over to my laptop and meet you to work on the problem.
I must emphasize that I agree with the previous posts and irrespective of your level of computer knowledge in the end it will be far better for you to be able to work it out for yourself and thereby help you in the future should a similar occurrence re-occur.
Thanks a bundle for the replies everyone!
It must be a learning block is all i can think of...Same thing happened to me with Algebra!
Anyway, i would like to figure it out:
So in APX mode i should see teh Gtab as a drive/device right? I think i did did before i messed everything up last week - so drivers were installed etc..
Now i do not.
Shoudl i take it apart and hit the reset button like the other thread shows?
Is there another way?
BTW i was on stock 1.1 3588 previously, so if i do get into APX mode and download the mediafire link posted, is that the correct download for someone still on 1.1?
@Hendge..... I don't want to pre-empt any reply or advice by fosser2 who is far more knowledgeable than I am. But as I read your reply it seems to me that you are uncertain as to what exactly "APX" mode is. You get into APX mode from a "powered off" tab by holding down the "Power Button" at the same time holding down the "Volume Down" rocker (as you look at the tab from the front in landscape mode then the "Volume Down" is the LEFT hand side of the rocker).
(1) With tab "off" connect with mini usb to your PC
(2) Perform the above operation i.e. power and volume down depressed, keep both pressed until you see the blank screen mentioned in (4)
(3) You should now get the "splash" screen which if you haven't altered anything will be the 3 birds
(4) After about 2 seconds the screen will go blank and you are now in APX mode
(5) I am taking you at your word that you have already installed the usb drivers on your PC
(6) Now we will accept that you have already downloaded fosser2's zip file and on your PC have unzipped it to a folder (let's call it FOSSER2 or whatever you want)
(7) If you look in that folder at the files you will see a file named something like ... nvflash_gtablet.bat... It might or might not be that exact name but it will be the only file in that folder with a ... .bat extension.
(8) Now with your tab connected and in APX mode, on your PC run the .bat file.
(9) A DOS Type command prompt box will open on your PC and you will see a lot of lines of text telling you what is happening.
(10) When all is finished it will say "Press Enter to continue....."
(11) Press "Enter" and the box will disappear and on your tab screen you should see a line of white text at the top left hand corner.
(12) Turn off your tab by pressing the power button, disconnect from PC and re-boot tab. If all has gone ok it should re-boot.
I have to tell you that not everything I've said above may work out because I've had to guess as to fosser2's intentions.
If you follow what I have said you may well brick your tab ..... I can't accept blame if you do as my only intention is to attempt to help you BUT there is that risk.
Good Luck
metpolds said:
@Hendge..... I don't want to pre-empt any reply or advice by fosser2 who is far more knowledgeable than I am. But as I read your reply it seems to me that you are uncertain as to what exactly "APX" mode is. You get into APX mode from a "powered off" tab by holding down the "Power Button" at the same time holding down the "Volume Down" rocker (as you look at the tab from the front in landscape mode then the "Volume Down" is the LEFT hand side of the rocker).
(1) With tab "off" connect with mini usb to your PC
(2) Perform the above operation i.e. power and volume down depressed
(3) You should now get the "splash" screen which if you haven't altered anything will be the 3 birds
(4) After about 2 seconds the screen will go blank and you are now in APX mode
(5) I am taking you at your word that you have already installed the usb drivers on your PC
(6) Now we will accept that you have already downloaded fosser2's zip file and on your PC have unzipped it to a folder (let's call it FOSSER2 or whatever you want)
(7) If you look in that folder at the files you will see a file named something like ... nvflash_gtablet.bat... It might or might not be that exact name but it will be the only file in that folder with a ... .bat extension.
(8) Now with your tab connected and in APX mode, on your PC run the .bat file.
(9) A DOS Type command prompt box will open on your PC and you will see a lot of lines of text telling you what is happening.
(10) When all is finished it will say "Press Enter to continue....."
(11) Press "Enter" and the box will disappear and on your tab screen you should see a line of white text at the top left hand corner.
(12) Turn off your tab by pressing the power button, disconnect from PC and re-boot tab. If all has gone ok it should re-boot.
I have to tell you that not everything I've said above may work out because I've had to guess as to fosser2's intentions.
If you follow what I have said you may well brick your tab ..... I can't accept blame if you do as my only intention is to attempt to help you BUT there is that risk.
Good Luck
Click to expand...
Click to collapse
Do this and you will be fine
Hi guys, I don't know if there are similar threads within this section, and have decided to post this thread. It has been long since I have touched my i9003, having migrated to the i9000 itself.
Anyway, here's the thing. This phone got submerged about a year ago in the water (due to my brother's stupidity) and the camera did not function anymore as well as the home button. To make things worse, the phone's warranty was already over when it happened. Back then I was tinkering with using ADB and Odin in order to flash custom ROMs and whatnot, then suddenly, I seemed to have pressed a wrong button of sorts during one of the flashing processes and it landed me on the Android system recovery <3e> screen. Now normally, this would be relatively easy with a working home button, because it would be just a simple press to freedom, but of course, as I have stated before, the button was broken.
I tried at first using ADB, but the PC didn't pickup the device/didn't recognize it. It's also recognized as a CDC Abstract Control Model and not the usual standard USB recognition.
Given the circumstances, would it still be possible to recover and reboot back to at least the home screen?
!n0x said:
Hi guys, I don't know if there are similar threads within this section, and have decided to post this thread. It has been long since I have touched my i9003, having migrated to the i9000 itself.
Anyway, here's the thing. This phone got submerged about a year ago in the water (due to my brother's stupidity) and the camera did not function anymore as well as the home button. To make things worse, the phone's warranty was already over when it happened. Back then I was tinkering with using ADB and Odin in order to flash custom ROMs and whatnot, then suddenly, I seemed to have pressed a wrong button of sorts during one of the flashing processes and it landed me on the Android system recovery <3e> screen. Now normally, this would be relatively easy with a working home button, because it would be just a simple press to freedom, but of course, as I have stated before, the button was broken.
I tried at first using ADB, but the PC didn't pickup the device/didn't recognize it. It's also recognized as a CDC Abstract Control Model and not the usual standard USB recognition.
Given the circumstances, would it still be possible to recover and reboot back to at least the home screen?
Click to expand...
Click to collapse
Just hold the power button till the phone's screen dims out, phone should reboot into Android.
I forgot to state that every time I reboot it via long pressing the power button, it immediately goes to the 3e Recovery.
Good day to all. I'm here resorted to ask about my problem here because I really can't handle it. I been googling for days. I'm ran out of resources from both google and tablet. So, I hope you can help me here. Note I'm going to write this in FULL detail here, so expect this to be a extremely long post. (I been warning you) So here goes....
Anyone uses the brand Ramos?(kind of unpopular brand) I use Ramos W21, it's been using it around 1 year and a half, and it endured a lot of problems, but fixed by researching on online forums and apply various methods there. Now, I think it's finally gave up...
One time, when I opened it and play my usual apps and browsing, it caused the errors " unfortunately
google.process.gapps has stopped", unfortunately browser has stoped",and "unforturnately google play has stopped". Then, I tried to clear data the similar apps in settings as usual, and even disabling them. Then more errors exploded, and "unfortunately launcher has stopped" appears. The menu screen(where the usual wallpaper and shortcut apps are located) turns black, while my running apps are still there running. When I pressed the back key to exit the app, now only tons of errors from the launcher appears endlessly(while the screen is black.
The time I finally turned it off by hard reset it made its way to the main problem: the bootloop.
Okay, here's where the thing gets real. It opens with the usual ramos logo, but the next one is a silver flashing android logo instead of enlarged ramos logo with spinning fire from the letter o(which is NOT my usual boot up screen) When I turned it off, it reopens again up to flashing silver android logo and the cycle repeats, even with pin reset until battery dies out. No recovery mode, so I can't use it to fix this. USB connections can't be recognized when inserted to PC. And no, the tablet is not rooted, and I don't customized anything, no mods, and no fancy roms. Just using a stock rom.
So now what? All I have here is just a sd card slot, which I think there's hope in there. Right now it has two options, deal with it and fix with all of might, or repair it in the nearest repair shop(something that is pretty risky, a lot of fakes and robbers here)
Well, this is the first time I post here, so sorry for anything that goes wrong. Thanks in advance.
Hi, thank you for using XDA Assist. It sounds like a rouge app has replaced your boot animation. Rather than try to chase that down and try to fix it I'd flash the stock firmware and start all over. Unfortunately there is very little about your device on XDA. So you'll probably have to google that.
Solved!!!
Update: I FINALLY FIXED IT!!! IT WAS A MIRACLE!!! O.O
After I keep on wrecking it's power buttons and volume buttons, I discovered something decisive!
This tablet actually HAS RECOVERY MODE! Again, it has a recovery mode! However, the way how to input it is very unique compared to most devices, including other devices from the same brand!
Now having the power of recovery state, I first selected "wipe data cache". The old large Ramos logo with spinning fire appeared again! But it's still bootlooping. So I went back on recovery state, selected "factory reset" and boom, IT BOOTS LIKE BRAND NEW!!! (sacrificing my old data though)
Okay, I don't want this recovery mode powers to be kept only by me. So I'm going to share it to all Ramos users,especially the model W21, like right now!
1. To do this, you need power button and volume up button.
2. While bootlooping, hold the power button and volume button at the same time and it will turn it off(Then expect it to turn on back up again automatically)
3. When it opens up again to the small Ramos logo(no fire animation), now RELEASE the POWER BUTTON ONLY, and keep holding the volume up button. Note, this is important! If you do anymore than this, it will either black out, go bootlooping once again, or ultimately, nothing.
4. Keep holding the volume up button, then the ramos logo will disappear, and now it will enter to our holy grail, RECOVERY MODE! Congratz!
Now when you finally have a normal working Ramos tablet again, you may go there again by turning it off by "Power Off" (assuming that your tablet is open) then holding the power and volume up(then follow above!)
I hope this will help a ton for Ramos users! :laugh:
I'm glad you got it working. You should post your solution here, http://forum.xda-developers.com/general/general More people with your device will look there than in the Assist forum. Name the post something like [SOLVED] RAMOS Bootloop Problem
jd1639 said:
I'm glad you got it working. You should post your solution here, http://forum.xda-developers.com/general/general More people with your device will look there than in the Assist forum. Name the post something like [SOLVED] RAMOS Bootloop Problem
Click to expand...
Click to collapse
Well thank you then for the link. Gotta go there!
Thread closed.
I just downloaded the update for Cyanogen Mod 13 and I clicked install then my phone powers on (no matter what buttons I press; power, power and volume up and home) it has the Samsung S5 logo and the text "Recovery booting..." (as well as the other warranty text stuff). It then quickly flashes the screen with the Android and cog logo with the text "Installing system update" for the shortest time (making it almost impossible to read the text) it then flashes this screen on and off every 5-10s for the rest of the time. I thought that the screen maybe just a little glitchy but the "update has been running for almost an hour now. How can I fix this problem if my phone doesn't allow me to put it into recovery mode .
So I spent about 3 hours trying to fix this problem trying every combination of buttons to press on boot as well as trying to make my phone detectable or something like that. Let my Mum try fiddling with it (she has no idea what she doing with new tech) some how she managed to press the buttons just right. It went into download mode and I was able to flash it with an update of TWRP using ODIN and it rebooted and started up. If you haven't already try putting it into download mode, I've heard getting the timing right can be tricky when your phone is doing unusual things. Now I'm unsure whether to try updating again but I might try wiping and going back to a stable 12.1.
Mod Edit:
Thread closed as ODIN fixed it