Hi!
My P500 was originally Gingerbread 2.3.3, than I used CM 7.2 with AmonRa 3.0.6 recovery for a year.
So I tried to flash KitKat (http://forum.xda-developers.com/showthread.php?t=2589303), and got some issues.
I flashed ClockworkMod Recovery 6.0.4.6 (Jan/14), than the ROM (v8), and the installation worked well.
Before the reboot, CWM says:
"root access possibly lost. Fix?
this can not be undone"...
Whatever I choose, I got that black screen with
"fastboot mode started
udc_start()".
Thaaaan, I see this: http://forum.xda-developers.com/showthread.php?t=2439466
and tried to downgrade SU to v1.55. But the CWM got an error, and cannot install (even with AmonRa)...
After all, I can't get KitKat working, and got back to AmonRa recovery and CM 7.2.
To complete the "good vibe", my Android can't get AT ALL connect through USB, so I can't test any ADB command.
I don't know where I'm doing wrong... Any directions??
Thanks!!!!
SOS
This^. Exactly this is what I am suffering from right now and I am amazed how identical the issue is. I hope the OP doesn't mind if I added some more info since I didn't wanna create a new thread when one is already made recently.
Here is some info in brief regarding my issue.
Last OS: CynogenMod 7.2
Last CWM: 5.0.0.X
Target OS: Cynogen KittKat
Target CWM: 6.0.4.6 [January 2014 release]
Downloaded KittKat Rom from here: http://forum.xda-developers.com/showthread.php?t=2589303
Downloaded CWM from here: http://forum.xda-developers.com/showthread.php?t=2564767
Everything went fine when I flashed the CWM first and it entered the new recovery mode without a hitch. But the trouble began after I flashed the KittKatt Rom. Though initially everything installed just fine but in the end just before restart, this came:
"root access possibly lost. Fix?
this can not be undone"...
For safe measure I chose "Yes" and that's where my phone apparently got "soft-bricked" cause it rebooted into fastboot mode with this message
"fastboot mode started
udc_start()".
I looked around and found a "solution" for this kind of issue here: http://forum.xda-developers.com/showthread.php?t=1088046
I followed instructions to the letter but my the LG Mobile support tool refused to identify my phone. Since I figured it might have been a driver issue so I installed PDAnet instead to get stuff working. The only hitch was that PDAnet would hang on "Updating PDAnet to your phone" option. I sat their staring at it for an hour or so and figured something was wrong like my phone wouldn't allow to install anything on itself since my debugging wasn't enabled, though I am not sure about this one.
In any case I checked device manager and my ADB drivers were fine so I ran the three recovery commands in DOS anyway and they all executed without a hitch. I jumped for joy but my happiness was short lived since the phone booted back into recovery mode and now I am basically stuck up the creek without a paddle. I could really use some expert advice here just like the OP cause I really am not sure what went wrong and where. I would really like to fix this rather than flash and start the whole phone up from scratch if possible.
Regards,
LonerPrime
PS: Long time reader but this is my first post here so greetings to the xda community.
LonerPrime said:
This^. Exactly this is what I am suffering from right now and I am amazed how identical the issue is. I hope the OP doesn't mind if I added some more info since I didn't wanna create a new thread when one is already made recently.
Here is some info in brief regarding my issue.
Last OS: CynogenMod 7.2
Last CWM: 5.0.0.X
Target OS: Cynogen KittKat
Target CWM: 6.0.4.6 [January 2014 release]
Downloaded KittKat Rom from here: http://forum.xda-developers.com/showthread.php?t=2589303
Downloaded CWM from here: http://forum.xda-developers.com/showthread.php?t=2564767
Everything went fine when I flashed the CWM first and it entered the new recovery mode without a hitch. But the trouble began after I flashed the KittKatt Rom. Though initially everything installed just fine but in the end just before restart, this came:
"root access possibly lost. Fix?
this can not be undone"...
For safe measure I chose "Yes" and that's where my phone apparently got "soft-bricked" cause it rebooted into fastboot mode with this message
"fastboot mode started
udc_start()".
I looked around and found a "solution" for this kind of issue here: http://forum.xda-developers.com/showthread.php?t=1088046
I followed instructions to the letter but my the LG Mobile support tool refused to identify my phone. Since I figured it might have been a driver issue so I installed PDAnet instead to get stuff working. The only hitch was that PDAnet would hang on "Updating PDAnet to your phone" option. I sat their staring at it for an hour or so and figured something was wrong like my phone wouldn't allow to install anything on itself since my debugging wasn't enabled, though I am not sure about this one.
In any case I checked device manager and my ADB drivers were fine so I ran the three recovery commands in DOS anyway and they all executed without a hitch. I jumped for joy but my happiness was short lived since the phone booted back into recovery mode and now I am basically stuck up the creek without a paddle. I could really use some expert advice here just like the OP cause I really am not sure what went wrong and where. I would really like to fix this rather than flash and start the whole phone up from scratch if possible.
Regards,
LonerPrime
PS: Long time reader but this is my first post here so greetings to the xda community.
Click to expand...
Click to collapse
The way back home without buggy LG Mobile anything: Remove and replace batter, press home, volume-down and power keys simultaneously. Can be a bit tricky but will get you back in recovery. I assume you did that backup before playing. Restore it to get the phone back up.
Two ways to get your Kitkat:
1. Using the Version-8 install, do a clean install and be sure to choose an item in the various menu panes. Should work with this and then you need to reinstall and setup everything.
2. Take the "nightly" and install normally doing the requesite steps in the backup.
Thank you, but– Nvm fixed it.
@Dovidhalevi
Thank you for your amazing advice. I was able to get into recovery and restore from my nandroid backup. *Thank god I did that*
But kittkat ROM is still being a pain. I decided to read the logs of version 8 of the ROM a bit more closely and found this:
Upgrading from CM-10.2 or older / Fresh (First time) Installation: Now DON'T WIPE ANYTHING (Data/Factory reset, Wipe Cache partition, Dalvik Cache, Format System) everything have built in Aroma Installer. Simply flash through sdcard or adb sideload, Follow the Aroma Menu. Finish and Reboot device. Avoid Facebook, Whatsapp, Viber, Hangout apps while selecting apps to be flash, it may gives you fastboot mode. Done!!!
I decided to try my luck once more and disabled all those apps during the installation. But just before rebooting my phone lost root access again and asked if I wanted to fix it or not and then it froze again on LG logo afterwards. Another force restart and it went straight into fastboot mode. Had to do another restore to get my phone working on the older backup.
Now I know it isn't the CWD cause I am running that with my older Cynogen 7.2 OS and its rebooting without a hitch unlike kittkat which mysteriously loses root access...
I really apologize if I am being a bit noobish. Even though hardware/networking/linux[Red Hat] is like playing in my backyard, android itself is a new concept to me, hence I really appreciate all the help I can get on this to work.
MAJOR EDIT: I finally found the root of the problem and got my KitKat munching! The issue was, yep you definitely guessed it, human error... that human being me and if the original OP did everything like I did then I am guessing he made the same mistake.
What I did was, I didn't read the Aroma installer's text thoroughly enough during the installation process. At one point there comes a choice of partitions and the installer asks you to choose one of the following: *Please forgive me this is not the exact quote of the text but roughly along the same lines as memory serves*
A) Install if you are coming from a previous version of the ROM.
B) Install if you are coming from a different ROM all together.
Trust me, the way I put it makes me look like an idiot for not choosing the right choice but the actual text combined with reading carelessly on the fly ended up me botching up my initial attempts to install the new ROM. Point being you have to choose the second option and then install like usual. Following that method I wasn't faced with fastboot mode in the end and after 5 to 10 minutes of loading I was playing with the KittKat ROM. Once again I apologize for bothering you good folks and I am grateful for the guidance to the person above me.
Kind Regards,
LonerPrime
I'll try
LonerPrime said:
@Dovidhalevi
MAJOR EDIT: I finally found the root of the problem and got my KitKat munching! The issue was, yep you definitely guessed it, human error... that human being me and if the original OP did everything like I did then I am guessing he made the same mistake.
What I did was, I didn't read the Aroma installer's text thoroughly enough during the installation process. At one point there comes a choice of partitions and the installer asks you to choose one of the following: *Please forgive me this is not the exact quote of the text but roughly along the same lines as memory serves*
A) Install if you are coming from a previous version of the ROM.
B) Install if you are coming from a different ROM all together.
Trust me, the way I put it makes me look like an idiot for not choosing the right choice but the actual text combined with reading carelessly on the fly ended up me botching up my initial attempts to install the new ROM. Point being you have to choose the second option and then install like usual. Following that method I wasn't faced with fastboot mode in the end and after 5 to 10 minutes of loading I was playing with the KittKat ROM. Once again I apologize for bothering you good folks and I am grateful for the guidance to the person above me.
Kind Regards,
LonerPrime
Click to expand...
Click to collapse
Glad you fixed your phone!! I forgot to say what I did to "fix" it...
Read error... maybe???
I'll try as soon as I get home, with results!! Thanks!!!
I did that... =/
yes.. i was doing right. All the 6 times I tried...
And tried again now, just to be sure, and FASTBOOT again.
=/
jpesci said:
I flashed ClockworkMod Recovery 6.0.4.6 (Jan/14), than the ROM (v8), and the installation worked well.
Before the reboot, CWM says:
"root access possibly lost. Fix?
this can not be undone"...
Click to expand...
Click to collapse
All newer recoveries have this behavior. Because you are running a custom ROM and recovery, you should select "No" when prompted to disable recovery flashing.
Did you try the Key combos suggested by @Dovidhalevi to manually enter in to CWM?
As a worst case scenario, view this post to see how to restore your device to stock.
It's fixed, but no Kitkat...
shinobisoft said:
All newer recoveries have this behavior. Because you are running a custom ROM and recovery, you should select "No" when prompted to disable recovery flashing.
Did you try the Key combos suggested by @Dovidhalevi to manually enter in to CWM?
As a worst case scenario, view this post to see how to restore your device to stock.
Click to expand...
Click to collapse
Oh, sorry. Maybe bad explanation. I did get it fixed. All the "x" times, heheh =)
I just got in recovery by pressing home+vol up+power, and flashed back my older ROM. Now I'm trying CM 10 by Jenkins.
The problem isn't the "fastboot" message itself... but don't get Kitkat working =/
But thanks for the reply anyway!
kitkat by mukulsoni... ui stops with multiple popupd
M stuck.. i have successfully flashed kitkat by mukulsoni.. thanks. BUT UI DOES NOT START... it starts with so many popups... eg. Unfortunately voice dialer has stopped. Unfortunately bluetooth share has stopped. Unfortunately com.google.process.gapps stopped. Unfortunately com.android.systemui has stopped . Unfortunately clock has stopped. Unfortunately kitkat+ launcher stopped....
what to do. Should i get back through backup 4m recovery.. or u can help me wid kitkat .. feeling so sad..
amit2411 said:
M stuck.. i have successfully flashed kitkat by mukulsoni.. thanks. BUT UI DOES NOT START... it starts with so many popups... eg. Unfortunately voice dialer has stopped. Unfortunately bluetooth share has stopped. Unfortunately com.google.process.gapps stopped. Unfortunately com.android.systemui has stopped . Unfortunately clock has stopped. Unfortunately kitkat+ launcher stopped....
what to do. Should i get back through backup 4m recovery.. or u can help me wid kitkat .. feeling so sad..
Click to expand...
Click to collapse
Boot in to your recovery and try wiping your cache and dalvik cache.
still no working
I wish I could get these popups.
Is there something else to do??? I tried everything, everyway... Always get "fastboot mode started / udc_start()".
jpesci said:
I wish I could get these popups.
Is there something else to do??? I tried everything, everyway... Always get "fastboot mode started / udc_start()".
Click to expand...
Click to collapse
Maybe I can help... Are you flashing the same download every time? It's possible that your download managed to get corrupted. Try redownloading the ROM. I'd suggest redownloading the newest recovery also.
Now I'm going to list my ROM installation method for comparison. I personally have NEVER had an issue installing a ROM on any Optimus One variant. And I have 3 of them...
Boot device to your current recovery. CWM 6.0.45+ is compatible with CM10 - CM11 only. If you are currently running an older recovery, make a backup of your ROM with your current recovery first. Now if running an older recovery, Select "Install from zip" and install CWM 6.0.4.5+ or equivalent. Then go to "Advanced" and select "Reboot Recovery". We should now be in your new recovery. 1) Select "Wipe data/factory reset". This will wipe cache, data, .android_secure, and sd-ext.
2) Select "Advanced" then "Wipe Dalvik Cache". When done, return to recovery main menu.
3) Select "Mounts and storage". Choose "Format /system" and then confirm the action. Go back to main menu.
4) Select "Install from zip". Now we can install KitKat. Browse to and select your KitKat ROM and confirm installation.
5) If your device was old baseband ( originally running Android 2.2.2 or older ) then you will also need to flash the old baseband patch found here.
6) If you wish to flash a GApps package, that should be done now, or optionally after booting the device and letting it boot in to the ROM for the first time.
7) Go back to the main menu and select "Reboot device". If prompted to disable recovery flashing, select "NO". First boot will take 3 - 5 minutes.
shinobisoft said:
Maybe I can help... Are you flashing the same download every time? It's possible that your download managed to get corrupted. Try redownloading the ROM. I'd suggest redownloading the newest recovery also.
Now I'm going to list my ROM installation method for comparison. I personally have NEVER had an issue installing a ROM on any Optimus One variant. And I have 3 of them...
Boot device to your current recovery. CWM 6.0.45+ is compatible with CM10 - CM11 only. If you are currently running an older recovery, make a backup of your ROM with your current recovery first. Now if running an older recovery, Select "Install from zip" and install CWM 6.0.4.5+ or equivalent. Then go to "Advanced" and select "Reboot Recovery". We should now be in your new recovery. 1) Select "Wipe data/factory reset". This will wipe cache, data, .android_secure, and sd-ext.
2) Select "Advanced" then "Wipe Dalvik Cache". When done, return to recovery main menu.
3) Select "Mounts and storage". Choose "Format /system" and then confirm the action. Go back to main menu.
4) Select "Install from zip". Now we can install KitKat. Browse to and select your KitKat ROM and confirm installation.
5) If your device was old baseband ( originally running Android 2.2.2 or older ) then you will also need to flash the old baseband patch found here.
6) If you wish to flash a GApps package, that should be done now, or optionally after booting the device and letting it boot in to the ROM for the first time.
7) Go back to the main menu and select "Reboot device". If prompted to disable recovery flashing, select "NO". First boot will take 3 - 5 minutes.
Click to expand...
Click to collapse
Thanks for explanation!! But... still nothing.
I did EVERY SINGLE STEP like you said. Except for baseband, cause my phone was originally 2.3.3. But all new downloads...
After flashing, try to reboot... DAMN! "root access possibly lost..." YES/NO, gives me same problem. I read another thread about this erros, people said about SU. Can it be? I tried to flash another SU version, but CWM return an error too =/
jpesci said:
I wish I could get these popups.
Is there something else to do??? I tried everything, everyway... Always get "fastboot mode started / udc_start()".
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2559363 try this.
voltaire23 said:
http://forum.xda-developers.com/showthread.php?t=2559363 try this.
Click to expand...
Click to collapse
Ah, thanks man! But my problem isn't the "brick" itself, but the frustration of can't get kitkat working, hehe.
By the way, I think KDZ method dangerous, by many reports that you can find all through the web. In all 217897254179 times I tried Kitkat without success, I just rebooted in recovery mode (hold HOME+VOL UP+POWER button), and recovered the last CWM backup.
But thanks to the effort =)
jpesci said:
Ah, thanks man! But my problem isn't the "brick" itself, but the frustration of can't get kitkat working, hehe.
By the way, I think KDZ method dangerous, by many reports that you can find all through the web. In all 217897254179 times I tried Kitkat without success, I just rebooted in recovery mode (hold HOME+VOL UP+POWER button), and recovered the last CWM backup.
But thanks to the effort =)
Click to expand...
Click to collapse
I am considering the jenkins build from here: http://download.androidarmv6.org/_builds/
can anyone help with finding the smallest gapps that will fit?
Edit:No need
Related
Hi guys,
I was trying to unroot my nexus S using the guide found here (http://forum.xda-developers.com/showthread.php?t=1088494&highlight=unroot)
After clicking start on odin, it started to do its thing and then it failed all of a sudden. and now im stuck on the yellow triangle Downloading screen. I press and hold power nothing happens. i dunoo what to do. I am a complete noob. someone please help. I am attaching the image of the what the screen looks like (http://postimage.org/image/3dhtlidg/)
and here what odin looks like now (http://postimage.org/image/3eqh3vpg/)
ok guys, i took out the battery and put it back on and turned it on again and it powered on but now i have no signal or empty bars. it shows aeroplane now.. i tried different sims no difference.. i get no service.. i think this odin fail at radio damaged my radio somehow..someone please advise me.. please .. i did volume up button + power and tried to go to recovery but i get triangle with exclamation mark. so i took out the battery and reboot it to normal. no signal. just the aeroplane icon. Also when i put the phone in USB mode, i see folders like clockworkmod and im able to see my back up that i made before doing all this. However not able to access it in the phone. I also see that all my apps and everything is gone, but i still some apps folders in the usb mode. what should i do?
First, your link goes to a NxS 4G guide, but you state you got a NxS (non-4G). Which one you got?
Following is for the __NxS only__ (as I have no experience with the 4G):
If a little Droid is holding the "triangle with exclamation mark" then that is normal as you're accessing the stock recovery, press vol up + power again to see the recovery.
Once done that go here and get a full rom flashable zip for your device. Get a "signed" version if available as those are flashable via stock recovery. (*) Put the zip on your sdcard, reboot into recovery again, wipe everything the options allow you to, install zip from sdcard, reboot. You're done with an unrooted, stock phone.
If there's no "signed" you gotta flash the cwm recovery via fastboot first (USB drivers seem to be working and your phone is recognized). Go mount and storage and choose "Mount USB storage" Then continue after the (*) and leave out the reboot after putting the zip on your sdcard.
yeh crap i just realized.. i used the guide for nexus s 4g.. i have the gsm model (non-4g). from here in canada. damn i feeel so stupid... fml..
ok so behind the battery the sticker says my phone model is I9020A and then I went to the page yu asked.. and i found the following two of interest.
Android 2.3.4/GTJ61/UCKE1 Radio/KA3 Bootloader
Works on: I9020A
Unofficial, unsigned, must flash through ClockworkMod Recovery. Contains recovery, radio and bootloader.
Courtesy of XDA forum member scott8281
Android 2.3.4/GRJ22/XXKD1 Radio/KA3 Bootloader
Works on: I9020T, I9023
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
My phone before all this mess occured was on GRJ22 build. So can i use the 2nd one here since its official and signed whereas the first one is unsigned. and like u suggested i should try to find a signed rom.
next question, how do i "wipe everything the options allow you to" ..
also when i do vol up + power and scroll to recovery and press power.. google logo comes up and then the droid with white triangle that has exclamation mark. I just cannot load into recovery :$
sorry for being so noob at this :$ But thanks for helping...
Breathe.
No, you cannot use the second flash "Android 2.3.4/GRJ22/XXKD1 Radio/KA3 Bootloader" This is not for the I9020A variant.
I can tell you how to get everything back to stock. Are you willing to unlock the bootloader? There is no full signed rom for the I9020A.
You need to:
http://wiki.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide#Unlocking_the_Bootloader
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
Then install
http://forum.xda-developers.com/showthread.php?t=1033269
Then update back to 2.3.4
http://android.clients.google.com/p...5b.signed-sojua-GRJ22-from-GRI54.286d814d.zip
Then lock the bootloader.
Oh okay. yes please I am willing to do anything to get this phone working to normal. and by the way, when i do volume up+power, i see locked stated - unlocked. doesn't that mean my bootloader is already unlocked. I also see the lock icon along with google when i turn on the phone.
cool6324 said:
You need to:
http://wiki.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide#Unlocking_the_Bootloader
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
Then install
http://forum.xda-developers.com/showthread.php?t=1033269
Then update back to 2.3.4
http://android.clients.google.com/p...5b.signed-sojua-GRJ22-from-GRI54.286d814d.zip
Then lock the bootloader.
Click to expand...
Click to collapse
okay so basically i start following the guide from the point it says Installing the ClockworkMod Recovery Image since my bootloader is already unlocked.
one question though, right now when i connect my phone through usb, i am able to see the folder such as clockworkmod in sd card, so if im installing clockworkmod recovery, am i just reinstalling this again?
also for flashing cyanogen mod, i would choose the "method via recovery" right since my phone is not really rooted right now. I don't have the ROM manager app. Thanks a lot cool6324
The rom has to be for your phone. If your phone is an i9020A you got to take the first one you marked red.
@cool6324, I think his phone's bootloader is unlocked as his phone was rooted before and later then 2.3.x, means no Gingerbreak to avoid unlocking the bootloader.
---
forpulse, you got ADB set up and ready to go? (If not go to: http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/ to learn how to set it up)
If yes, download the rom to your pc. Also download the cwm recovery here. Boot phone into Android. Copy the rom on your sdcard (needs to be in the top folder). Copy the cwm recovery into the \tools (see below, (*))
Keep your phone connected via USB to your pc. Unmount the sdcard (the Droid got to be green not orange anymore), make sure you activated "USB Debugging" in settings (not sure of the right english terms should be in: "Apps/Programs" > Development). Now start a command prompt (windows key + r, then type "cmd", hit enter). (*)Navigate to the \tools inside ADB/SDK folder you created already or created by following the unlockr guide I linked above. To navigate simply type "cd <drive letter>:\<folder name>\tools and confirm with enter. Once inside the right folder you can start using the following commands:
adb devices (this should return you your device's id)
adb reboot bootloader (this takes a few secs and your phone will boot into bootloader menu)
fastboot flash recovery <recovery image name>.img (this should return a time and an "OK")
Now you can continue on your phone:
Navigate into recovery
Wipe > Factory reset, cache and dalvik cache
Mount and Storage > format system/boot
Install zip from sdcard, choose the ROM's name, install, confirm
"Go back" until you can choose "reboot system now", phone should boot into unrooted, stock Android now.
---
one question though, right now when i connect my phone through usb, i am able to see the folder such as clockworkmod in sd card, so if im installing clockworkmod recovery, am i just reinstalling this again?
Click to expand...
Click to collapse
That clockworkmod folder contains so called "Nandroid backups". This contains a full backup of your phone (__if__ you made one).
Did you make one before messing up your phone? If yes, follow my guide above to the point your going into recovery and just hit "backup and store", "restore" instead of flashing a new rom. I'd recommend to "wipe" "factory reset", "cache" and "dalvik cache" before though.
rentaric said:
The rom has to be for your phone. If your phone is an i9020A you got to take the first one you marked red.
@cool6324, I think his phone's bootloader is unlocked as his phone was rooted before and later then 2.3.x, means no Gingerbreak to avoid unlocking the bootloader.
---
forpulse, you got ADB set up and ready to go? (If not go to: http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/ to learn how to set it up)
If yes, download the rom to your pc. Also download the cwm recovery here. Boot phone into Android. Copy the rom on your sdcard (needs to be in the top folder). Copy the cwm recovery into the \tools (see below, (*))
Keep your phone connected via USB to your pc. Unmount the sdcard (the Droid got to be green not orange anymore), make sure you activated "USB Debugging" in settings (not sure of the right english terms should be in: "Apps/Programs" > Development). Now start a command prompt (windows key + r, then type "cmd", hit enter). (*)Navigate to the \tools inside ADB/SDK folder you created already or created by following the unlockr guide I linked above. To navigate simply type "cd <drive letter>:\<folder name>\tools and confirm with enter. Once inside the right folder you can start using the following commands:
adb devices (this should return you your device's id)
adb reboot bootloader (this takes a few secs and your phone will boot into bootloader menu)
fastboot flash recovery <recovery image name>.img (this should return a time and an "OK")
Now you can continue on your phone:
Navigate into recovery
Wipe > Factory reset, cache and dalvik cache
Mount and Storage > format system/boot
Install zip from sdcard, choose the ROM's name, install, confirm
"Go back" until you can choose "reboot system now", phone should boot into unrooted, stock Android now.
---
That clockworkmod folder contains so called "Nandroid backups". This contains a full backup of your phone (__if__ you made one).
Did you make one before messing up your phone? If yes, follow my guide above to the point your going into recovery and just hit "backup and store", "restore" instead of flashing a new rom. I'd recommend to "wipe" "factory reset", "cache" and "dalvik cache" before though.
Click to expand...
Click to collapse
Yes, i do have ADB set up ready to go but if I understood your right. Do I follow what your saying after following cool6324's guide or don't follow that and do what u suggest. I have not yet started out on his suggestion as I was reading everything and trying to understand. Also, when i go to download the CWM recovery. it says NS4G, so is this again for the sprint 4G model? or it also works on non-4g model which is what i have. I am just confirming this since I don't want to make the same mistake as above. :$
forpulse said:
Yes, i do have ADB set up ready to go but if I understood your right. Do I follow what your saying after following cool6324's guide or don't follow that and do what u suggest. I have not yet started out on his suggestion as I was reading everything and trying to understand.
Click to expand...
Click to collapse
The linked guide's result is equal to mine if you don't flash the CyanogenMod, but the rom cool6324 linked. Just make sure you get a full rom for _your_ device this time
rentaric said:
Copy the rom on your sdcard (needs to be in the top folder). C
Click to expand...
Click to collapse
which top folder are u talking about. is it ".android_secure" ? and I don't extact the ROM zip file right? i just put that directly in "top folder" ? and just to make sure i'm using "Stock-GTJ61-I9020A-Unsigned"
(100mb) found from one of your earlier links.
When I went to download CWM recovery from ur provided link, I saw different ones.. is it only for colour different purposes or there is actually a valuable difference amongst them? or do i download them all... i sound so stupid right now asking such questions:$
I'm really sorry If I am frustrating you with these stupid questions.. i've only had this phones for 2 days and its my first time with android... but thanks again...
forpulse said:
which top folder are u talking about. is it ".android_secure" ? and I don't extact the ROM zip file right? i just put that directly in "top folder" ? and just to make sure i'm using "Stock-GTJ61-I9020A-Unsigned"
(100mb) found from one of your earlier links.
When I went to download CWM recovery from ur provided link, I saw different ones.. is it only for colour different purposes or there is actually a valuable difference amongst them? or do i download them all... i sound so stupid right now asking such questions:$
I'm really sorry If I am frustrating you with these stupid questions.. i've only had this phones for 2 days and its my first time with android... but thanks again...
Click to expand...
Click to collapse
Good morning.
Yes, the difference between those recoveries is just color of text. !!Don't get the 4G version!!
The top folder is the one you access when the usb storage pops up on your pc. The zip file goes in there unextracted.
File size seems correct for a full rom.
Sent from my Nexus S using XDA App
rentaric said:
Good morning.
Yes, the difference between those recoveries is just color of text. !!Don't get the 4G version!!
The top folder is the one you access when the usb storage pops up on your pc. The zip file goes in there unextracted.
File size seems correct for a full rom.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Good Morning,
Alrighty, I think I have understood everything now, although, I'm at work right now so I will begin the process 8 hours later today and get back to you with the results... thanks for being so patient...
Hey rentaric,
i followed your guide and im delighted to say that my phone is back to normal or at least i think so lol.. everything is worked out and so far the phone is running fine. i made calls and what not.. the only issue i got now is... auto-rotate does not work. i cannot type text in landscap mode even though i got auto-rotate checked in display settings.. even in gallery, photos do not auto-rotate.. pretty much auto-rotate does not work whether i turn it on or off :S ..would you happen to anything about this? nonetheless, thank you so much for helping me out..
forpulse said:
Hey rentaric,
i followed your guide and im delighted to say that my phone is back to normal or at least i think so lol.. everything is worked out and so far the phone is running fine. i made calls and what not.. the only issue i got now is... auto-rotate does not work. i cannot type text in landscap mode even though i got auto-rotate checked in display settings.. even in gallery, photos do not auto-rotate.. pretty much auto-rotate does not work whether i turn it on or off :S ..would you happen to anything about this? nonetheless, thank you so much for helping me out..
Click to expand...
Click to collapse
Glad to hear it worked out for you to some degree. Sadly I have no solution to the not workign sensor part. See, I'm not pro myself, I'd just try widgetsoid app first. It got an rotate on/off function in its widget, if that wouldn't work for me I'd prolly flash another rom to see if it's the sensor trying to bully me. In the end hardware failures are still a possibility even on teh NxS.
sounds good.. no worries... i have a feeling this phone might have a defective sensor since it did not work also before with the older ROM which was GRJ22 xxkd1 ... but anyway i'll search/ask around if anyone knows anything... thanks again man...
Hello there,
I've just got a Nexus S which has ICS installed. I must say I've used Android before but am no expert, especially when it comes to the whole ROM scene. While I am a very technical user, from my online research I haven't yet been able to figure out how to best go about the downgrade to 2.3.6.
My concern being that this is not stock anymore and I would not want to brick it by treating it as stock and simply following the standard downgrade or ROM flash directions.
I am attaching a screenshot for everyone to see exactly what I've got on the device.
Any help with this would be immensely appreciated!
Cheers.
Since you said you're a technical user I assume you know how to use fastboot and stuffs. To downgrade to GingerBread, you only need to install a custom recovery (ClockWorkMod) for your phone model and flash a full OTA package. I guess that's all
Well if the phone already has ICS installed, I'm pretty sure it also has Clockworkmod Recovery(aka. CWM or CWR).
Try this:
Turn off your phone.
Turn it on by HOLDING DOWN the power button AND the volume up button. After 2-3 sec. you should see a menu. Scroll down 2 clicks with the volume down button, you should land on 'Recovery '. Press the power button to enter CWR. (Clockworkmod Recovery)
If this procedure takes you to another menu, then you have a functioning CWR. And if so, I would recommend trying one or more of the fine roms in this forum under 'Android Development'. Many of these roms have a lot of features and fixes that you would miss once you've had them.
Try it out, and happy flashing.
PS. To flash most roms, download the rom on your mobile. (it's a zip-file) and go to CWR. Choose 'wipe data/factory reset' and then go to 'advanced' and there you should choose 'wipe dalvik cache'. Go back, choose 'install zip from sdcard' and then 'choose zip from sdcard'. Locate the rom you downloaded and choose it. This will flash the rom. Go back and choose 'reboot system now'. The first boot on any rom will allways take longer than usual. Usually about 2min. Enjoy! ;-)
Sent from my Google Nexus S using xda premium
swaipa said:
Well if the phone already has ICS installed, I'm pretty sure it also has Clockworkmod Recovery(aka. CWM or CWR).
Try this:
Turn off your phone.
Turn it on by HOLDING DOWN the power button AND the volume up button. After 2-3 sec. you should see a menu. Scroll down 2 clicks with the volume down button, you should land on 'Recovery '. Press the power button to enter CWR. (Clockworkmod Recovery)
If this procedure takes you to another menu, then you have a functioning CWR. And if so, I would recommend trying one or more of the fine roms in this forum under 'Android Development'. Many of these roms have a lot of features and fixes that you would miss once you've had them.
Try it out, and happy flashing.
PS. To flash most roms, download the rom on your mobile. (it's a zip-file) and go to CWR. Choose 'wipe data/factory reset' and then go to 'advanced' and there you should choose 'wipe dalvik cache'. Go back, choose 'install zip from sdcard' and then 'choose zip from sdcard'. Locate the rom you downloaded and choose it. This will flash the rom. Go back and choose 'reboot system now'. The first boot on any rom will allways take longer than usual. Usually about 2min. Enjoy! ;-)
Sent from my Google Nexus S using xda premium
Click to expand...
Click to collapse
Not necesarilly, CWM not always remains flashed and have to reflash repeatedly. Try what was recommended here, if not, download Rom manager and reflash.
That worked. Turns out I already had everything I needed to install from an archive.
So I downloaded the official 2.3.6 full ROM and got it installed.
The problem I am facing now is that as soon as the phone boots up, I get a sequence of errors, the first one being "The process com.google.process.gapps has stopped unexpectedly. Please try again."
This gives me a "Force close" button, and that's about it. Then there are subsequent errors for android.process.acore, com.android.providers.calendar and then it just sort of loops back and forth between those.
Unfortunately the problem here being that I cannot tap the Android to get started or anything like that. It looks like I am pretty much stuck.
swaipa, I followed your instructions and everything worked seamlessly.
Any clue as to why I am getting all of these issues now?
Edit: nevermind, I just did the same thing again and it seems to be working well!
Kudos my friend, you're on to a life of flashing.. ;-)
Sent from my Nexus S using xda premium
cant go beyond recovery menu using i9023 with ICS any ideas ?
I able to downgrade from 4.0.3 to 2.3.6
Here is what I did...
http://kishanrathod.blogspot.com/2011/12/downgrade-nexus-s-from-403-to-236.html
hey
http://en.miui.com/a-1.html try this steps and it will work.
At "Downloading flashing tools and ROM pack" instead of ther rom, you should download the official OTA for your model from here http://forum.xda-developers.com/showthread.php?t=1063664.
good luck...
i have a i9023 a put first 2.3.3 and i make de update to 2.3.6.
good luck!
just a question please :
What does "install unlocked boot" or "fast boot" mean , Will it unroot the device ? and after that , If I will install a stock 2.3.6 ROM , will I return 100% factory (including the stock recovery) ?
i`ve check my recovery and it is stock like i had before.
after you finish downgrade LOCK the device using UNLOCK start bat and write LOCK instead of UNLOCK.
euskode said:
That worked. Turns out I already had everything I needed to install from an archive.
So I downloaded the official 2.3.6 full ROM and got it installed.
The problem I am facing now is that as soon as the phone boots up, I get a sequence of errors, the first one being "The process com.google.process.gapps has stopped unexpectedly. Please try again."
This gives me a "Force close" button, and that's about it. Then there are subsequent errors for android.process.acore, com.android.providers.calendar and then it just sort of loops back and forth between those.
Unfortunately the problem here being that I cannot tap the Android to get started or anything like that. It looks like I am pretty much stuck.
swaipa, I followed your instructions and everything worked seamlessly.
Any clue as to why I am getting all of these issues now?
Edit: nevermind, I just did the same thing again and it seems to be working well!
Click to expand...
Click to collapse
im also getting this same issue from installing GB via odin.
cant work out how to fix it.
i dont fully understand swipa's instructions there
Hi all, I just ordered a Chinese B63M phone at cect-shop.
Nice phone with great specs.
I alreadu know how to root it, but are there already custom Roms available?
Could'nt find a lot of info, just a Russion version.
B63M... thats my phone
Henkdrenth said:
Hi all, I just ordered a Chinese B63M phone at cect-shop.
Nice phone with great specs.
I alreadu know how to root it, but are there already custom Roms available?
Could'nt find a lot of info, just a Russion version.
Click to expand...
Click to collapse
Now that makes us 2 people who owns a B63M and got it from cect-shop.
What I find out about their phones is that it may not easily allow you to perform some insider operations, for instance, maybe its me but I could not find any custom recovery installed and this led to my first issue after I rooted, and installed the ROM manager, I saw the 'fix permission' and clicked it hoping to resolve my force close issues and it asked me to reboot after performing the process but it never got out of the boot, the loop continued, trying to boot into recovery become impossible but somehow a combination got me into a mode where I was able to clear flash and this took me back to a pre factory flash good thing I backed up titanium so I cld restore my apps and upgrade.
Right now I have tried to flash and the screen has gone blank yet the phone is responding to touch as I can hear sounds when the screen is clicked, indicating that its not bricked I just cant see anything going on (this is my current situation and seriously looking for help).
Lastly, I am trying to find out the htc equivalent to this b63m, it looks htc but I cant be sure which of the htc has been more or less cloned... this is going to help with a lot of things if known.
Cheers
Hi there,
If you are looking for a custom recovery, try this forum, altough you have to translate it because it is in German.
Lots of people there with our phone end they know how to get a custom recovery on it.
Cect is German
Henkdrenth said:
Hi there,
If you are looking for a custom recovery, try this forum, altough you have to translate it because it is in German.
Lots of people there with our phone end they know how to get a custom recovery on it.
Click to expand...
Click to collapse
Yeah thanks, I have also stumbled on the site forum before but I cld not get something out of it, maybe I have not taken time enough to search, I am back on it now and hope I get a solution to the blacked out screen problems I have after flashing.
You know cect-shop is German, they are a German company in China... I am talking to them on skype and hoping they can help me out but they seem pretty busy or cant be bothered because their response is so much delayed or even not at all.
Well technoforum has a special B63M section with all tools required.
They also have nice custom roms like a Cyanogen fork.
I also don't speak Italian, but with the help of Google translate I'm getting pretty far.
But I do let Google translate from Italian to English, that gives me the best result.
Good luck!!
Do you also get no working screen after a reboot with both volume + and power button?
That should get you to the recovery screen without any ROM drivers.
Very correct, no screen even in recovery
When I do the button combination, I believe that it may have responded to my combination for recovery mode but I just cant see anything on the screen, it just remains the same way it was... maybe it graphics issue, as in is the graphics is messed up for some reason or resolution issue, you wont see anything being displayed.
I am just guessing here but all I did was to simply flash an update.zip from sd card.
That is very strange, since flashing a rom does not affect the screen of the recovery boot.
The rom video driver gets only active during the boot process of the rom.
In the past I had some boot problems with my Wildfire start-up that I solved by removing the SIM card and SD card, removed the battery for some minutes and them booted completely resetted.
You could try that, if that does not solve the problem, the only way to wipe the phone back to factory-reset is doing it blind.
After I get my phone I could make a step-by-step guide so you could get to the reset menu...
Another possibility is to re-flash a fresh recovery img to the phone. Since I don't know what was in your update.zip, you could messed up the recovery menue, or even the bootloader.
Re-flashing those could also help and you don. t need the display from the phone, since you use the PC for that.
Here it is
Here is the update.zip I flashed. http://chinamobiles.org/downloads.php?do=file&id=618&langid=4
I am a bit surprised myself that the screen is blanked out but the phone seem to be working still.
I have removed both SIMS and SD card plus battery several times etc. nothing changed.
You said ''After I get my phone I could make a step-by-step guide so you could get to the reset menu...'', I hope you get your phone soon tho, and i can see the step-by-step guide you made.
I have actually flashed recovery into it using flash tool, ODIN dont seem to see the phone (at least the yellow box saying COm4 or 5 is not showing), I can see the phone using adb but when I say adb reboot download or recovery, something happens but I cant see what it is.
I too have a B63M...!!! Spice Mi-350n...........
If you need a moded recovery, i can port it for you........but you need to follow some instructions...i'll give them tomorrow!!
Waiting on you... I hope my blank screen gets sorted.
balamu96m said:
I too have a B63M...!!! Spice Mi-350n...........
If you need a moded recovery, i can port it for you........but you need to follow some instructions...i'll give them tomorrow!!
Click to expand...
Click to collapse
Ahh thanks man... Ii will wait to hear from you tomorrow, I aim in UK and depending on what time zones you are in but I hope to find you online to connect again.
I hope you have understood my particular issue here tho, the screen if blank even tho the fone seem to be alive and it follows the boot sequence, I can even find it using 'adb devices' command, it just the screen gone blank.
Someone suggested it may be the boot.img but I dont know about that.
Cheers
I'm from India - Local time here is GMT+5:30......!!
So, here you go !!
B63M= MTK6573 + 650mhz + Android 2.3
So, one modded recovery.img can't be used for every B63M.......this is because a different B63M phone will have a different recovery.img..........(hope u understand)
Backing up everything:
1) ROOT is necessary. It is recommended to put the phone in 'Airplane mode' so that it won't disturb the process and make sure you have ~500 mb space in SD card.
2) Download 'BackUpTools.rar' from HERE and extract it to your SD Card. You'll have 2 folders - 'gscript' and 'Install'.
3) Install 'GScriptLite.apk' from gscript folder.
3) After installation, open the 'GScriptLite' application -> Menu -> Add Script.
4) Tick 'Needs SU ?'
5) Click 'Load File' and select 'Back23.sh' and then select 'save'
6) Now Click on 'Back 23' and Super User will ask for Permission and allow it. Nothing more to touch. Wait for few minutes. After few mins, it will say 'Auto Close is Cancelled'. Now its safe to close.
7) Your Back-Up will be in 'backup_' folder located in your SD card's root.
It will have files named ' firmware.info, preloader.img, nvram.img, seccnfg.img, uboot.img, boot.img, recovery.img, secstatic. img, misc.img, logo.img, expdb.img, cache.img, system.img, data.img' in that folder. Copy it to your computer and keep it at a safe place. More Over if you are posting in the forums or sharing it online, don't include ' data.img, cache.img and nvram.img' as they contain your personal information.
Here i need two files.One is recovery.img and the other is firmware.info.
If you give both, i can port one for your phone !! Also mention your phone's model name/number because, without that it is not possible.
xdadeem said:
Here is the update.zip I flashed. http://chinamobiles.org/downloads.php?do=file&id=618&langid=4
HTML:
I am a bit surprised myself that the screen is blanked out but the phone seem to be working still.
I have removed both SIMS and SD card plus battery several times etc. nothing changed.
You said ''After I get my phone I could make a step-by-step guide so you could get to the reset menu...'', I hope you get your phone soon tho, and i can see the step-by-step guide you made.
I have actually flashed recovery into it using flash tool, ODIN dont seem to see the phone (at least the yellow box saying COm4 or 5 is not showing), I can see the phone using adb but when I say adb reboot download or recovery, something happens but I cant see what it is.
Click to expand...
Click to collapse
That was the problem, you flashed only the update, not a complete Rom.
I suggest you make a complete re-flash vorm scratch, so refash a fresh recovery.img and re-flash als a new Rom.
You can vind one at technoforum' as earlier mentioned
I thot you shd read my latest.
Ok guys I appreciate this a lot.
Here at this point I think you shd hear my developments before taking any further actions or suggestions.
aha thanks, I did just that and it worked although it is still blank at the beginning of boot but later something shows up on screen and completes boots.
Remember I mentioned that someone suggested it might be a boot.img problem... well, I used flashtool to flash a boot image and I can say it worked, I now have the visuals, even tho the screen is still blank at boot start but soon after it picks up and its working, now I have the phone again.
so @balamu96m, my issue was basically the screen, without seeing anything I cannot follow the back up suggestion you gave me here, but now I can see it again.
A couple of additional issues tho...
1- I checked the kernel and it has changed from 2.3.5 into 2.3.4 and >In the current ROM flash I have lost a couple of capabilities like Flashlight, camera etc
2- I followed this link http://www.technoforum.it/forum/viewtopic.php?f=73&t=3351 to flash recovery and it says Successful with the green Circle -OK-... but I still cant get boot into recovery either when I use the keys combi or when I try to boot into recovery in mobileuncle tools, it just goes blank and stays like so until I have to remove the battery and restart boot normally.
3- From the same link above they have the Golight ROM in part 2 after recovery in part 1, I am assuming this a good ROM to flash and the things I lost will get back, but I still cant boot into recovery.
Coming back to the response from balamu96m... Should I still go ahead with what yu suggested and provide you the files details you want? both recovery.img and firmware.info... I am asking because I no longer have the original ROM that came with the phone and like I said I cant even get into Recovery after I tried flashing a new recovery.img, this one from the same link above (see the recovery.img inside the 'Recovery Moddata' file from the 'UPDATEB63MRecovery2012' download file.)
Great to hear that you have visual again!
You still have root yes?
The golight rom from technoforum is a good one.
I expect mine any moment now so I can customize mine too.
Good luck!
xdadeem said:
Ok guys I appreciate this a lot.
Here at this point I think you shd hear my developments before taking any further actions or suggestions.
aha thanks, I did just that and it worked although it is still blank at the beginning of boot but later something shows up on screen and completes boots.
Remember I mentioned that someone suggested it might be a boot.img problem... well, I used flashtool to flash a boot image and I can say it worked, I now have the visuals, even tho the screen is still blank at boot start but soon after it picks up and its working, now I have the phone again.
so @balamu96m, my issue was basically the screen, without seeing anything I cannot follow the back up suggestion you gave me here, but now I can see it again.
A couple of additional issues tho...
1- I checked the kernel and it has changed from 2.3.5 into 2.3.4 and >In the current ROM flash I have lost a couple of capabilities like Flashlight, camera etc
2- I followed this link http://www.technoforum.it/forum/viewtopic.php?f=73&t=3351 to flash recovery and it says Successful with the green Circle -OK-... but I still cant get boot into recovery either when I use the keys combi or when I try to boot into recovery in mobileuncle tools, it just goes blank and stays like so until I have to remove the battery and restart boot normally.
3- From the same link above they have the Golight ROM in part 2 after recovery in part 1, I am assuming this a good ROM to flash and the things I lost will get back, but I still cant boot into recovery.
Coming back to the response from balamu96m... Should I still go ahead with what yu suggested and provide you the files details you want? both recovery.img and firmware.info... I am asking because I no longer have the original ROM that came with the phone and like I said I cant even get into Recovery after I tried flashing a new recovery.img, this one from the same link above (see the recovery.img inside the 'Recovery Moddata' file from the 'UPDATEB63MRecovery2012' download file.)
Click to expand...
Click to collapse
You flashed a recovery, but that is not working ah?? Oh God!!
Why did you do that bro??
Do you have any backup of the stock one??
If you dont have, then i have 2 ideas....one idea is to flash something else such that your fone won't boot....now you can send your phone back to the manufacturer and ask them to reflash everything!!!
The other idea, i'll tell you after sometime!!
It was always so
balamu96m said:
You flashed a recovery, but that is not working ah?? Oh God!!
Why did you do that bro??
Do you have any backup of the stock one??
If you dont have, then i have 2 ideas....one idea is to flash something else such that your fone won't boot....now you can send your phone back to the manufacturer and ask them to reflash everything!!!
The other idea, i'll tell you after sometime!!
Click to expand...
Click to collapse
The reason i flashed recovery initially was that my phone went into a boot loop and I was unable to get into recovery, after a while somehow i figure it out and cleared flash and then restored my phone apps and co and got on fine.
But if I could not get into recovery it means that there was not stock recovery on my phone or it got missing somehow. This I have to ask Henkdrenth since he is getting the same phone from the same shop too, but there was no recovery in my B63m, I already heard there is a recovery problem with the phone anyway, and thats why I flashed recovery and it worked but then I flashed ROM and the screen went blank, which is what got me to this forum.
I did not just go and flash recovery, it because there was none on the phone in my opinion.
xdadeem said:
The reason i flashed recovery initially was that my phone went into a boot loop and I was unable to get into recovery, after a while somehow i figure it out and cleared flash and then restored my phone apps and co and got on fine.
But if I could not get into recovery it means that there was not stock recovery on my phone or it got missing somehow. This I have to ask Henkdrenth since he is getting the same phone from the same shop too, but there was no recovery in my B63m, I already heard there is a recovery problem with the phone anyway, and thats why I flashed recovery and it worked but then I flashed ROM and the screen went blank, which is what got me to this forum.
I did not just go and flash recovery, it because there was none on the phone in my opinion.
Click to expand...
Click to collapse
Now, is the recovery working??
Does the phone boot properly??
Wrong section. Moving to general.
YES and NO
balamu96m said:
Now, is the recovery working??
Does the phone boot properly??
Click to expand...
Click to collapse
After many troubles, I found a mod for w690 which is the build version of my phone, I could not boot to recovery so used flashtool and when I load the scatter text of the one I found, it automatically load in every item on the list including recovery and boot img , etc, so I flashed these to my phone... and for the first time I was back in how the phone came to me,
Gingerbread has now returned to 2.3.5.
One thing I have noticed is that the phone freezes on me and then reboots?
I still cannot boot into recovery, I tried this again using mobileuncle tools...
It seem that I have flashed my phone which is good, but I was unable to wipe cache because I could not boot into recovery to do this which may be the source of the current freeze and reboot.
Can I solve this using the mobileuncle or what can I do to wipe cache, if that is the problem
Well, received mine, rooted it an flashed a new recovery from technoforum using myuncletools.
All went well, so I suggest you do also a fres re-flash with a proper recovery.
Hope that should solve your problem.
Edit: moved from my tablet to my PC to look for the link of a correct recoveryfile for you.
First, load this recovery.
Unpack it and put the content to the root of your SD card.
Use myuncletools to flash this recovery.
Now you should have a usable custom recovery that allows you to factory-reset and wipe your phone
Install a fresh rom
How to? Look here
Noob looking for all the help he can get!!!!!
Hi, I recently rooted my Samsung Galaxy S 2 for T-mobile, because I was sick of waiting for jelly bean to officialy come out for it, and ever since it's been a nightmare. I was running the most recent version of ICS that t-mobile has for my phone.
I got instructions on how to root at the unlocker . com
After that, I went to the Cyanogenmod website, went through their wiki and found the zip for my phone, (I also put the gapps zip on too). I booted into Clockwork mod recovery, did a back up, did a data wipe, but not a cache wipe as the instructions i was using from theunlocker.com did not say I had too. Flashed both zips from my external sd, then restarted. It booted with the Cyanogenmod name inside two spining circles. I left it like this knowing it may take a bit, and I come back 20 mins later expecting it to be done and it is in the same place i left it 20 mins ago. I decide to take out the battery, boot into Clockworkmod and restore. It booted fine back into ICS and all my data was still there, except all of the apps I had stored on my sd card would not work/show up with the icon it was supposed to. when i tapped it, it said that it was not installed on the phone. I decided not to let this worry me, as i decided to use ROM Manager app to do the job instead.
When i opened ROM Manager it prompted me to flash Clockworkmod recovery, so I did. It flashed my phone to Clockworkmod Recovery v6.0.2.7. I then went to download Cyanogenmod 10 for my phone. It downloaded with gapps 4.1. When I tapped install, it restarted my phone into Clockworkmod recovery, but did not install anything, just sent me to the main menu. So I decided i'd try getting the zip from the Cyanogenmod website again. I booted into Clockworkmod, wiped data AND cache this time. installed the zips, and restarted. I get the same problem, stuck at the cyanogenmod boot up circles spining. so i turn off my phone, boot back into clockworkmod, restore, and now i'm stuck in boot cycle with the stock ICS.
Please can anyone help me!?!?!?!
airplane888 said:
Noob looking for all the help he can get!!!!!
Hi, I recently rooted my Samsung Galaxy S 2 for T-mobile, because I was sick of waiting for jelly bean to officialy come out for it, and ever since it's been a nightmare. I was running the most recent version of ICS that t-mobile has for my phone.
I got instructions on how to root at the unlocker . com
After that, I went to the Cyanogenmod website, went through their wiki and found the zip for my phone, (I also put the gapps zip on too). I booted into Clockwork mod recovery, did a back up, did a data wipe, but not a cache wipe as the instructions i was using from theunlocker.com did not say I had too. Flashed both zips from my external sd, then restarted. It booted with the Cyanogenmod name inside two spining circles. I left it like this knowing it may take a bit, and I come back 20 mins later expecting it to be done and it is in the same place i left it 20 mins ago. I decide to take out the battery, boot into Clockworkmod and restore. It booted fine back into ICS and all my data was still there, except all of the apps I had stored on my sd card would not work/show up with the icon it was supposed to. when i tapped it, it said that it was not installed on the phone. I decided not to let this worry me, as i decided to use ROM Manager app to do the job instead.
When i opened ROM Manager it prompted me to flash Clockworkmod recovery, so I did. It flashed my phone to Clockworkmod Recovery v6.0.2.7. I then went to download Cyanogenmod 10 for my phone. It downloaded with gapps 4.1. When I tapped install, it restarted my phone into Clockworkmod recovery, but did not install anything, just sent me to the main menu. So I decided i'd try getting the zip from the Cyanogenmod website again. I booted into Clockworkmod, wiped data AND cache this time. installed the zips, and restarted. I get the same problem, stuck at the cyanogenmod boot up circles spining. so i turn off my phone, boot back into clockworkmod, restore, and now i'm stuck in boot cycle with the stock ICS.
Please can anyone help me!?!?!?!
Click to expand...
Click to collapse
First things first: the Jelly Bean update brings with it changes to the core file system organization in Android. Google "Android 4.2 Updates, Multi-User, and TWRP | TeamWin" for a brief explanation from TWRP (which, by the way, I recommend over ClockworkMod Recovery, although both can do the job). That, I believe, explains your missing data.
How are you obtaining your ROM/gapps zips? Are you downloading on your phone? If so, over wifi or mobile data? It is always a good idea to a) download on your computer and transfer the file to the phone and b) make a note of the MD5 checksum and verify the zip file before installing (any file browser worth its salt should be able to generate an MD5 sum). What it sounds like to me is your ROM download was borked in some way but it installed far enough to screw with your file system. I would recommend using your ICS backup to connect to a computer and load a ROM file downloaded from there before attempting to re-flash.
Maybe, just maybe you didn't clear cache and dalvik when installing cm. I had this problem and I realised I didn't wipe it. I wiped cache and dalvik cache from cwm and it booted fine.
Sent from my Xperia Mini Pro
ooddiittyy said:
First things first: the Jelly Bean update brings with it changes to the core file system organization in Android. Google "Android 4.2 Updates, Multi-User, and TWRP | TeamWin" for a brief explanation from TWRP (which, by the way, I recommend over ClockworkMod Recovery, although both can do the job). That, I believe, explains your missing data.
How are you obtaining your ROM/gapps zips? Are you downloading on your phone? If so, over wifi or mobile data? It is always a good idea to a) download on your computer and transfer the file to the phone and b) make a note of the MD5 checksum and verify the zip file before installing (any file browser worth its salt should be able to generate an MD5 sum). What it sounds like to me is your ROM download was borked in some way but it installed far enough to screw with your file system. I would recommend using your ICS backup to connect to a computer and load a ROM file downloaded from there before attempting to re-flash.
Click to expand...
Click to collapse
Thanks I will look into TWRP. I am getting my ROM/gapps zips straight from cyanogenmod's wiki for my phone, i get gapps from the link they provide. As for MD5, I do not know what that is other than it was generated when i backed up, and checked when i restored.
i have the same problem
i tried it with my galaxy fit s5670
i tried to flash cm-10.1-20130117-NIGHTLY-beni, some another version named of jelly bean pure rom and also TouchWiz_JB_V5
always the same thing it gets stuck at logo than nothing
i did everithing in order clear data, factory reset, clear cache, clear dalvik cache through cwm recovery
can someone help?
is it because of low int. space?
i found app named s2e to make sd card as int. memory but it didn't work
any suggestions?
thanks in advance
Here's my new problem, I'm stuck in boot loop with my restore of stock ICS, so when I go into download mode (+and- with power button while usb plugged in) I hear the "ching" that windows makes when you plug in a usb device, bu when I navigate to where removable disc should be in my computer, it is not there, so i don't know what to do, I just want my phone to work again, even if that means starting all over with stock ICS.
I appreciate your time and help.
airplane888 said:
Here's my new problem, I'm stuck in boot loop with my restore of stock ICS, so when I go into download mode (+and- with power button while usb plugged in) I hear the "ching" that windows makes when you plug in a usb device, bu when I navigate to where removable disc should be in my computer, it is not there, so i don't know what to do, I just want my phone to work again, even if that means starting all over with stock ICS.
I appreciate your time and help.
Click to expand...
Click to collapse
what ROM are you coming from?
Sounds to me like the new multi-user stuff
I experienced something similar and determined that the phone wasn't hung at that bootscreen -- it was busy moving my 18 gigs of stuff (i9300) from /storage/sdcard to /storage/sdcard/0. Apparently this is the "home data" folder for the primary user of a 4.2 device and CM10.1 (I'm assuming you're using that because of the problem) appears to be that way. It would have been nice to know beforehand that I should have just waited the 1/2-hour I needed (took about that long to move back what had been moved; very little hadn't)
So look for that 0 folder and move the contents up one -- your old ROM will (hopefully) be the way it was before. If you decide to go CM10.1 again, just wait, *really* long, at first boot -- or clean out your internal sd card to make the transition quicker.
---------- Post added at 11:06 PM ---------- Previous post was at 10:53 PM ----------
airplane888 said:
Here's my new problem, I'm stuck in boot loop with my restore of stock ICS, so when I go into download mode (+and- with power button while usb plugged in) I hear the "ching" that windows makes when you plug in a usb device, bu when I navigate to where removable disc should be in my computer, it is not there, so i don't know what to do, I just want my phone to work again, even if that means starting all over with stock ICS.
I appreciate your time and help.
Click to expand...
Click to collapse
You won't see it appear as removable storage because it's in download mode -- removable storage (and the later MTP mode) are done by the OS, and the downloader screen is much "dumber" than that.
HOWEVER, all is not lost!
Try get a ROM which you can flash with ODIN. Either something off of www . samfirmware . com (stock firmwares available there) or DarkyROM (darkyrom . com) (Sorry, can't post actual links because I'm apparently not allowed to until I've posted more stuff . I've found the S1 and S3 to be practically unbrickable in this regard -- I assume the S2 to be the same. ODIN can push a completely new ROM onto your device, rescuing it. If you download from samfirmware, there is a pdf with instructions available on their site, but it basically boils down to:
1) Download a ROM. If you are downloading a zip file, extract the .tar.md5 file inside somewhere -- this is the file you need to flash via ODIN
1) ensure you have the samsung drivers installed (they will be if you have Kies installed, otherwise google for them -- or ask, and I'll try to help)
2) put your phone into download mode (vol-down+home+power)
3) plug your phone into your PC
4) fire up ODIN, you should see a message about a connected device on-screen
5) click the "PDA" button, browse to the ROM image (the .tar.md5 file) and select it
6) the default options have always worked for me -- just click "Start". The process will take some time, but there is feedback in ODIN. Your phone should (after 1-5 minutes) reboot into a fresh, clean ROM.
If you installed a stock ROM from samfirmware.com, you'll have to go about rooting and installing Clockwork mod again. Hope this helps.
Hi everyone, hate for my first to be a call for assistance, but here goes. Bought an Asus tf300t earlier today. I unlocked the device, then attempted to begin walking through this guide(http://forum.xda-developers.com/showthread.php?t=1845377) in order to have root+jb. In order to install clockworkmod, set up fastboot. After getting an error of "cannot load" in fasboot for the recovery image, I gave up, used the cmd prompt to reboot the device. On reboot, the touch screen no longer responded. I went to recovery, wiped data, to no avail. Now its simply showing the welcome screen, where you choose english, but can't select start. I've rebooted, wiped, and swore. A lot. My OS is windows 7, if that helps. Thanks everyone.
Shourisha1 said:
Hi everyone, hate for my first to be a call for assistance, but here goes. Bought an Asus tf300t earlier today. I unlocked the device, then attempted to begin walking through this guide(http://forum.xda-developers.com/showthread.php?t=1845377) in order to have root+jb. In order to install clockworkmod, set up fastboot. After getting an error of "cannot load" in fasboot for the recovery image, I gave up, used the cmd prompt to reboot the device. On reboot, the touch screen no longer responded. I went to recovery, wiped data, to no avail. Now its simply showing the welcome screen, where you choose english, but can't select start. I've rebooted, wiped, and swore. A lot. My OS is windows 7, if that helps. Thanks everyone.
Click to expand...
Click to collapse
Do I understand correctly that you've never successfully installed a custom recovery on your tab? So how did you wipe data? You chose the fourth option in the stock recovery?
graphdarnell said:
Do I understand correctly that you've never successfully installed a custom recovery on your tab? So how did you wipe data? You chose the fourth option in the stock recovery?
Click to expand...
Click to collapse
There were only 3 options--Wipe Data, usb, and android. I'd had success rooting the tablet earlier, but believed I'd made an error somewhere so followed that guide to try and begin again from the beginning. The wipe wasn't what caused the issue. It was working fine, until the reboot using the cmd line. Thats what makes so little sense to me.
Shourisha1 said:
There were only 3 options--Wipe Data, usb, and android. I'd had success rooting the tablet earlier, but believed I'd made an error somewhere so followed that guide to try and begin again from the beginning. The wipe wasn't what caused the issue. It was working fine, until the reboot using the cmd line. Thats what makes so little sense to me.
Click to expand...
Click to collapse
You didn't have the RCK option on your recovery? You said the wipe wasn't the culprit and it was working fine. Did you get to reboot the tab successfully after the wipe? Now everything seems to work fine on your PC monitor doesn't mean it is so. Lots of people using NVflash derivatives witness a smooth transition on papers until they find out it isn't so. Reboot command from ADB doesn't do anything special. I can't think of it doing any damage to the firmware if successfully installed earlier.
graphdarnell said:
You didn't have the RCK option on your recovery? You said the wipe wasn't the culprit and it was working fine. Did you get to reboot the tab successfully after the wipe? Now everything seems to work fine on your PC monitor doesn't mean it is so. Lots of people using NVflash derivatives witness a smooth transition on papers until they find out it isn't so. Reboot command from ADB doesn't do anything special. I can't think of it doing any damage to the firmware if successfully installed earlier.
Click to expand...
Click to collapse
Uhm, well, its simply started registering touch again. Like nothing had happened. Makes me worry about the tablet itself. But, its working fine now, and I didn't do a thing. Sigh. I'm not sure. Not I just have to figure out why fastbooter keeps giving me the "cannot load recovery.img" error. Thanks for the help!
Sounds like you are on the old bootloader. Be careful about wiping.
I'd update to the latest Asus Stock ROM for your device from their website which will bring you up to the latest bootloader.