hi, i have a samsung intercept from vm. I used a SuperOneClick to delete some stock apps and somethings wrong my on-screen keyboard is completely gone and i keep getting this message saying something about the android process has unexpectedly ended please try again and some times it wont stop coming up and wont let me do anything. i deleted stock email app, some of the virgin mobile stuff I'm new to this as you can tell. please help and thank you
"the process com.google.process.gapps has stopped unexpectedly. please try again."
Rom and Recovery
I am assuming your phone is rooted so can you please tell me what ROM and recovery you are running?
its not rooted any more i used a temporary root i believe its on the stock rom i tried factory reset but it still the same without the apps and the missing keyboard, thanks for your reply
Adb?
jefe1026 said:
"the process com.google.process.gapps has stopped unexpectedly. please try again."
Click to expand...
Click to collapse
This tells me you basically deleted some system applications that support the Google applications like Gmail, Calendar, etc. Not a good thing lol. Next time when you are deleting "bloatware," don't delete anything that starts with com.google or com.system. These are the packages that help run android and google applications.
Incidently, Do you know what adb is? If so, have you ever used it?
ive seen adb when i ran superoneclick im tryin to learn all this i use to have an iphone and hackin that is pie compared to this cause there is so many android phones
Try Factory Reset
jefe1026 said:
ive seen adb when i ran superoneclick im tryin to learn all this i use to have an iphone and hackin that is pie compared to this cause there is so many android phones
Click to expand...
Click to collapse
Don't worry, the initial rooting process is the hardest part. After that, it only gets easier. Then you can put on whatever custom ROM you want and trust me, its awesome!
Anyway, I don't think you need to use adb juuust yet. Did you try to get to recovery mode yet and try to factory reset the phone?
To get to recovery mode on your Samsung Intercept, you hold, all these buttons at the same time, for a few seconds:
Volume Down, Call, and End buttons.
This will either bring you to recovery mode or have an option for recovery mode. Once there, there will be a setting to factory reset your phone. It will say something along the lines of "Wipe Data/Factory Reset" It won't delete anything on your SD card but wipes out all your apps and restores it to when you first used it.
yea i did that and the stuffs still missing : / im tryng to use the sw update to re install stock 2.1 but i keep getting "cannot open .bin file"
I had that problem too. What i did is connect my phone with samsung kies and that restored evrything back for me.
May that not help, try to flash it back with original firmware using odin
just search on this forum
This is the site that contains evry firmware of evry samsung phone:
samfirmware.com
you only have to register
i dont see my phone in the android section
I'm not having any luck with this... nothing seems to work
Don't Give Up!
jefe1026 said:
I'm not having any luck with this... nothing seems to work
Click to expand...
Click to collapse
Don't fret. You haven't bricked your phone yet.
Ok. I checked to see if any forum or site was hosting the original signed zip of the OS that came with your phone and I couldn't find any.
I have an idea though. Not sure if it might work but theoretically it should. Although your phone WAS rooted (aka. temporary root), its not anymore which means you don't have any custom firmware and are running stock.
IF you updated your phone to 2.2 froyo with the official update, then it should completely replace the OS and not only reverse the damage but upgrade it as well.
So you take the phone, put it into "Recovery Mode," and then use adb to push this zip (link below) on to the ROOT OF THE SDCARD. not anywhere else!
then in the recovery, select the "flash/update zip" option and select the new zip.
In theory, this should work. Cannot be sure so tread with caution!
Here is the link:
http://02ee24b.netsolhost.com/downloads/crowder/update.zip
This is the full article that explains how to root your phone after:
http://www.crawfordium.com/blog/?p=22
Best of Luck!!
Thanks I'll try it out
I got this "E:Error in /sdcard/update.zip (Status 7) Installation aborted. I tried formatting the sdcard and redoing it but i got same message again I also tried going into superoneclick and hitting unroot and it says its unrooted but i still get the (status 7) message :/
and the sw upgrade says cannont open .bin file
This might work!
I was reading through some Samsung Intercept forums for you and this looks promising:
http://forum.sdx-developers.com/int...e-to-froyo-2-2-with-no-baseband-modification/
Go through the first three steps and flash the stock 2.1 on to your phone and it should be restored to basic regular Android 2.1. It IS sprint's stock 2.1 for intercept not Virgin Mobile's but its ok because it doesn't replace Virgin Mobile's Baseband so its fine. Instead of seeing the Virgin Mobile boot up screen, it will show you a sprint boot up screen. No biggie.
Try it and tell me how it goes. remember to follow instructions carefully and to the tee.
OK NOW IM ON SPRINT 2.1 and my number works and now im going to try upgrading to 2.2 show i try doing it over the air or just do it manually?
i just did it manually now im going to try to root it
now how do i get superuser and all that good stuff with the roms i dont like the slapstick 1.4
Related
Hi, I am new to all of this, but Im a quick learner. I rooted my phone and have superuser permission. I have installed multiple applications that will help me to perform ROM installs all of which still do not help. I even tried the three button solution, however I am still getting the same message when I go into recovery mode. It is as follows: E: failed to varify whole-file signature then under that I get: E: signature verification failed, instalation aborted.
I tried applying sdcard update. zip, wiped out cache partition, factory reset, etc...
I have tried everything. I tried using Mod Manager, I get the downloads but then when i try to install after I make sure to click backup rom and clear cache, it boots to the rom screen, (not really sure what you guys call it, sorry) and I get that same message, the signature failed, et...
my phone info is as follows: SCH-I500, I500 Commercial Package_DL9 To EA28 (I think verizon automaticly updated for the emergency dial) code 200
hardware version i500.04 firmware version 2.1update.1, baseband version S:i500.04 V.EA28, kernel version 2.6.29 and last but not least build number SCH-I500.EA28
Now saying all of that, I tried all of the above steps prior to this automatic update and it still did not work. I still received the signature message.
I even tried Voodoo, as well as DL30, Superclean, none of which will pass the signature autentacation. I want to try to get past this as I am having my phone replaced due to burn in and want to get the steps right so I do not BRICK my phone after it has been replaced. If this one bricks, it wont matter to much because I will have the new one on Monday.
Any help would be greatly appreciated. I love this tecky stuff and want to be knowagable on how to get past this message so I can go full force on Monday.
Thanks,
EssyG
Also I checked the site and tried everything but still won't work.
Sent from my SCH-I500 using XDA App
You will need to flash a new Recovery via ODIN which you can find below for your Samsung Fascinate:
http://forum.xda-developers.com/showthread.php?t=782204
&
Also read this http://forum.xda-developers.com/showthread.php?t=790004
Thank you, up and running 2.2, will post screen latter! Now I need to get my old phone back to stock so I can send it back to veriazon. YOU ARE THE BEST!!
P.S. I love your idea about the 10 post allowence to post on other forums.
Essy G
If o.k. I will post what I did and that way new users will be able to follow directions. I am a newbe but have become addicted to this stuff. THANKS!!
now I bricked my phone... lol
Now let me start by saying I loved 2.2, no problems with it at all. but when battery ran out I wanted to clean stats in cwm green and the screen would not come up, sd would not mount any how I tried to start over, flashing oden, all the steps, but my drivers will not stay for some reason after flashing I need to uninstall the reinstall drivers or they are not recognized, really sucks, any how I got frustrated so while in odin I pulled the plug, lol literally, and now have a pic of a "phone" then ".." then triangle with (like my icon here)"!" then ".." picture of "computer". I called verizon and there sending me yet another phone. lol my question is, will they be able to unlock it and see that I had 2.2 on it? does anyone know what they do with the phones we send back? Basicly I want to know if they can unlock that being I can't. and if so, will they see the 2.2? Any sugestions?
Anyone there?
Any one there? Also I am debating, do I wait for official release. I heard it was coming out 2/22/11. If I put dl30 on new phone again and they release the update, will I still get the automatic update via verizon? If so will I lose root? Any comments on post #5? I can't believe I had it running I totally messed it up. Thank goodness when I called verizon I got two girls at tec support, lol while I am a girl, I am a tech lover, I acted like I had no idea what happened, well they didn't either, lol So just waiting on new phone to come in, yet again so I am getting everything ready to quickly install dl30 to new phone again. Hopefully I do not lose drivers again, as it seems that once I flash in odin, the hardware icon disappers as if drivers are not installed. any how, I was just wondering if anyone had an answer to post #5 so that when I return the phone, I am not caught, lol that would really stink! Plus I am board, took off of work because my kids are sick and now I have a bad cold also, so any comments would be great!! Besides I need to be here to sign for new phone.
Thanks,
Essy g
Hi, i`ve owned an infuse for a couple months now and i`m loving it. I bought it off somebody and it came pre-rooted. Superuser was working great, i was running rooted apps and everything was pretty awesome. However, i`ve just recently wanted to try something new. Such as flashing a new rom. I downloaded the zeus rom (i also have others), went into rom manager and tried to install. That didn`t work. So i tried to manually boot into clockworkmod recovery and install. That didn`t work. I think the main problem is how do i get into clockworkrecovery? Whenever i boot into it i lack very many options that i keep seeing from others. Everytime i try to boot into it it says
Copying media files
Successfully copied meida files
Manual Mode
Appling Multi-CSC
Installing Multi-CSC
can't access to system/csc/RWC/system/
Successfully applied multi-csc
and the options are
Android system recovery <3e>
Samsung Recovery Utils for BML
Enter: Power Key, Select: vol up/ vol down
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
Everytime i try to apply update from sdcard it says:
Failed to verify whole-file signature
Installation aborted.
I can't remember all of it but you get the just of the idea
I can't seem to figure this out and i dont think this is clockwordrecovery. I've tried various methods of rebooting using the CWM app, Rom Manager app, and the button pressing.
All i want to do is flash a new rom! Can anyone help?
P.S. It isn't a typo when i put "Successfully copied meida files", they actually spelt it meida.
Xparks said:
Hi, i`ve owned an infuse for a couple months now and i`m loving it. I bought it off somebody and it came pre-rooted. Superuser was working great, i was running rooted apps and everything was pretty awesome. However, i`ve just recently wanted to try something new. Such as flashing a new rom. I downloaded the zeus rom (i also have others), went into rom manager and tried to install. That didn`t work. So i tried to manually boot into clockworkmod recovery and install. That didn`t work. I think the main problem is how do i get into clockworkrecovery? Whenever i boot into it i lack very many options that i keep seeing from others. Everytime i try to boot into it it says
Copying media files
Successfully copied meida files
Manual Mode
Appling Multi-CSC
Installing Multi-CSC
can't access to system/csc/RWC/system/
Successfully applied multi-csc
and the options are
Android system recovery <3e>
Samsung Recovery Utils for BML
Enter: Power Key, Select: vol up/ vol down
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
Everytime i try to apply update from sdcard it says:
Failed to verify whole-file signature
Installation aborted.
I can't remember all of it but you get the just of the idea
I can't seem to figure this out and i dont think this is clockwordrecovery. I've tried various methods of rebooting using the CWM app, Rom Manager app, and the button pressing.
All i want to do is flash a new rom! Can anyone help?
P.S. It isn't a typo when i put "Successfully copied meida files", they actually spelt it meida.
Click to expand...
Click to collapse
You don't have cwm recovery yet.
Don't use ROM manager.
I made a thread on "how to." It's a collection of some things I've learned.
Start there.
The link is on my signature line
So where should i start? At the flashing part?
Xparks said:
So where should i start? At the flashing part?
Click to expand...
Click to collapse
Start here:
[REF] [HOW TO] [ROM Installation] Where to start?
Xparks said:
So where should i start? At the flashing part?
Click to expand...
Click to collapse
yes..follow gtg's CWM instruction set
So. I already started with the odin UCKD5 one. http://forum.xda-developers.com/showthread.php?t=1092021
and i already started into download mode. However, it now says downloading. and my computer was like "installing new hardware" then "could not install new hardware" and now my phone is stuck in the downloading screen that says do not turn off target. Odin has yet to pick up my phone....what now?
if you have root you can flash a cwm enabled kernel with sgs kernel flasher.
if you have froyo use the defuse or community kernel. or use gtgs thread for cwm without flashing a kernel.
if you have gingerbread then you will need to flash one of the custom kernels such as entropy dd, hellraiser, or infusion. gtgs cwm thread will not work on gingerbread.
My phone is rooted and running on gingerbread. But um. i have a more pressing concern at the moment....this downloading screen is freaking me out...
okay well i can't seem to figure any of this stuff out. any noone has replied so i just reset my phone so i can actually use it.
Some more information for those who can help is that the firmware is 2.3.3
Baseband version is I997RUXKG3
Kernel version
2.6.35.7-I997RUXKG3-CL366622
Build number
Gingerbread.uxkg3
Xparks said:
okay well i can't seem to figure any of this stuff out. any noone has replied so i just reset my phone so i can actually use it.
Some more information for those who can help is that the firmware is 2.3.3
Baseband version is I997RUXKG3
Kernel version
2.6.35.7-I997RUXKG3-CL366622
Build number
Gingerbread.uxkg3
Click to expand...
Click to collapse
that's Rogers firmware. use kernel flasher (easiest) and flash one of the popular gingerbread kernels. entropy dd is popular. once the kernel is on there You will have red cwm. that will allow you to flash whatever.
if you flash a rom it will include a kernel so don't worry about the minor incompatibilities that exist with att based roms.
So i'm currently on this thread
http://forum.xda-developers.com/showthread.php?t=1212795
with this in the other tab
http://forum.xda-developers.com/showthread.php?t=1289460
I'm not sure which kernel to download. But i'll try flashing a couple anyway
also i tried using heimdall/odin or whatever. It wouldn't pick up my phone in download mode. and thus couldn't install drivers.
well. I tried flashing one of the kernels. specifically
DD_02162012_A.zip - [Click for QR Code] (5.16 MB, 118 views)
So i flashed it using SGS kernel flasher. it said flashing....rebooting. And now it's stuck at the rogers logo. I have no clue what to do and i think it might be bricked. So if i could get someones help, perhaps step-by-step as i obviously cannot do this following the other instructions.
Xparks said:
well. I tried flashing one of the kernels. specifically
DD_02162012_A.zip - [Click for QR Code] (5.16 MB, 118 views)
So i flashed it using SGS kernel flasher. it said flashing....rebooting. And now it's stuck at the rogers logo. I have no clue what to do and i think it might be bricked. So if i could get someones help, perhaps step-by-step as i obviously cannot do this following the other instructions.
Click to expand...
Click to collapse
You are stuck in bootloop. Not bricked or even close to it. Read infused rom and flash it. If you cannot figure that out you should not be flashing. It's dead simple. Promise. Search it. It's in the dev thread. Called infused by gtg
Sent from my SAMSUNG-SGH-I997 using Tapatalk
thanks for the help so far. but i went here. http://forum.xda-developers.com/showthread.php?t=1116251
and the link no longer works. so what now. I can't get the files and therefore can't put anything into odin.
sigh. so i downloaded the files from someone who uploaded it again. Did everything. Succesful. only to have it be stuck in bootloop and samsung screen. Did what it said. pulled battery, replace, vol buttons and power key until recovery shows up. That doesn't happen. Instead i notice that instead of a rogers screen it says at&t and then goes to samsung screen. and then restarts again by going back to at&t. If i let go of the buttons it goes back to begin stuck at the samsung one. This has made so many problems for me.... just by trying to get clockworkmod. what do i do now?
Xparks said:
thanks for the help so far. but i went here. http://forum.xda-developers.com/showthread.php?t=1116251
and the link no longer works. so what now. I can't get the files and therefore can't put anything into odin.
Click to expand...
Click to collapse
Xparks,
You really should read up a bit. If you looked toward the end of that thread,
you will see that the file has been uploaded by another user to another site:
http://forum.xda-developers.com/showthread.php?t=1116251&page=40
i got that one already. i've passed that step. I'm now stuck in bootloop with at&t and samsung logo. Bootloop was supposed to be a rare occurence...and the instructions to work around it aren't working right now. I can't access recovery mode. Or anything for that matter.
Xparks said:
i got that one already. i've passed that step. I'm now stuck in bootloop with at&t and samsung logo. Bootloop was supposed to be a rare occurence...and the instructions to work around it aren't working right now. I can't access recovery mode. Or anything for that matter.
Click to expand...
Click to collapse
Download the drivers for the phone on the computer. If it does not work then, try heimdale. If you can not do this, then just ask me for the jtag guy, ill give you the link to the website. Mobiletechvideos uses jtag to recover the phone (taking it apart, hooking it up with a ton of wires lol). Keeps personal data, just recovers rom, or you can pay a little extra for him just to install whatever rom. It worked for me, you may have a broken usb controller like me all of a sudden.
I have kies but when i start it up it says please connect your mobile phone. And it doesn't pick up my phone. It probably shouldn't seeing how my phone is stuck. But i went to menu in kies and pressed install driver. But i'm not sure how to download my exact driver if kies can't even pick up my phone. But i ran the "zazig" program. and i'm installing the drivers from there. And i'm going to attempt to reflash using that since Odin didnt work before. The link is this http://forum.xda-developers.com/showthread.php?t=1331381
And it did that. But i don't what to do. I've been on xda reading forums all day and the only thread i can see relevent to mine is someone advising them to bring it back under warranty. Mines rooted. no warranty for me. I hope if it ever works again i can use it on rogers still because it says AT&T.....and i'm afraid to try and unlock it. because we know the last time i tried to do something.....
Odin can still detect it and i tried reflashing the unbrick stuff. No dice.
I am new here so please bear with me.
I have a "rooted" Nexus S i9020. When I bought it it had Android 4.0.4 installed. Recently I have been receiving a message telling me that a system update to Android 4.1 is ready to be installed. I have tried accepting the update, but halfway through it stalls and all I see is a triangle with an exclamation mark in it. The phone will then not respond and requires removal and refitting of the battery to restart it. Luckily, it has returned to working order with 4.0.4 still installed.
Is the phone not accepting the update because it is rooted?
Can I get the OTA update without erasing all data and settings?
I have an app. called Superuser v.3.1.3 on the phone. It has a box to tick marked "temp unroot" and another "OTA survival".
Would either of these tools be any use?
I have tried to understand all the information given on the forum posts but there is just too much to take in.
Can someone explain what I have to do to get the phone updated without "bricking" it?
When I enter Bootloader mode it says:
FIRST BOOT MODE
PRODUCTNAME HERRING
HW VERSION REV 11
BOOTLOADER VERSION I9020 XXKL1
BASEBAND VERSION I9020 XXKI1
SER.NO etc.
LOCK STATE LOCKED
Is this information helpful? I have read about "clockwork mods" and "Roms", but I don't know what you mean.
Thank you in advance.
Clockworkmod replaces your stock recovery and then giving you options to flash ROMs etc. If you want to learn more... start with the sticky threads in development.
Your phone is rooted so if you want to get the update you need to temp. Unroot using the superuser app like you mentioned. Try to get the update. Please report back if it helped
Sent from my Nexus S using xda app-developers app
so far no brick...
kwibis said:
Clockworkmod replaces your stock recovery and then giving you options to flash ROMs etc. If you want to learn more... start with the sticky threads in development.
Your phone is rooted so if you want to get the update you need to temp. Unroot using the superuser app like you mentioned. Try to get the update. Please report back if it helped
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
I ticked the "temp unroot" box and tried installing the update again. Same result. Install stops with exclamation mark triangle and grinning android. Restart by taking out the battery. Ok, I still have a phone. Running Android 4.0.4, but now there is no upgrade available and I will have to wait until they get around to offering it again before I can experiment further. If I check for updates, it tells me that I am up to date.
I wish that there was more information. I mean, what's the point of a triangle with an exclamation mark? Why can't it tell me what the problem is? Then I might be able to fix it.
Thank you for taking the trouble to reply.
PS. This device cost me £150, I really don't want to break it, and I would like to be in control of it. If I brick it, then I suppose I will sigh, then go down to Carphone Warehouse and sign a contract for a locked, dumbed down, boring, toe-the-line Samsung SIII. But I would much rather be the master of a rogue, rooted, rough and ready-for-anything Nexus S.
monkey shoulder said:
I ticked the "temp unroot" box and tried installing the update again. Same result. Install stops with exclamation mark triangle and grinning android. Restart by taking out the battery. Ok, I still have a phone. Running Android 4.0.4, but now there is no upgrade available and I will have to wait until they get around to offering it again before I can experiment further. If I check for updates, it tells me that I am up to date.
I wish that there was more information. I mean, what's the point of a triangle with an exclamation mark? Why can't it tell me what the problem is? Then I might be able to fix it.
Thank you for taking the trouble to reply.
PS. This device cost me £150, I really don't want to break it, and I would like to be in control of it. If I brick it, then I suppose I will sigh, then go down to Carphone Warehouse and sign a contract for a locked, dumbed down, boring, toe-the-line Samsung SIII. But I would much rather be the master of a rogue, rooted, rough and ready-for-anything Nexus S.
Click to expand...
Click to collapse
The triangle with an exclamation mark is most likely your stock recovery, that somehow got restored. Re-flash CWM or TWRP, then try to apply the OTA again.
Can't you be rooted and not have cwm?
Sent from my Nexus S using xda app-developers app
Install rom manager... the cwm 6.0.1.0 applies the ota.
Make sure you tick ota survival in superuser and after the ota cwm will ask you is you want to keep the stock recovery for next boot or keep the cwm.
Then it asks you to fix root rightz..select fix . And now you got the 4.1.1 rooted by ota
Sent from my Nexus S using xda app-developers app
monkey shoulder said:
I am new here so please bear with me.
I have a "rooted" Nexus S i9020. When I bought it it had Android 4.0.4 installed. Recently I have been receiving a message telling me that a system update to Android 4.1 is ready to be installed. I have tried accepting the update, but halfway through it stalls and all I see is a triangle with an exclamation mark in it. The phone will then not respond and requires removal and refitting of the battery to restart it. Luckily, it has returned to working order with 4.0.4 still installed.
Is the phone not accepting the update because it is rooted?
Can I get the OTA update without erasing all data and settings?
I have an app. called Superuser v.3.1.3 on the phone. It has a box to tick marked "temp unroot" and another "OTA survival".
Would either of these tools be any use?
I have tried to understand all the information given on the forum posts but there is just too much to take in.
Can someone explain what I have to do to get the phone updated without "bricking" it?
When I enter Bootloader mode it says:
FIRST BOOT MODE
PRODUCTNAME HERRING
HW VERSION REV 11
BOOTLOADER VERSION I9020 XXKL1
BASEBAND VERSION I9020 XXKI1
SER.NO etc.
LOCK STATE LOCKED
Is this information helpful? I have read about "clockwork mods" and "Roms", but I don't know what you mean.
Thank you in advance.
Click to expand...
Click to collapse
Unlock your bootloader first (will erase SD card) How to is in these.
http://forum.xda-developers.com/showthread.php?t=1007782
http://forum.xda-developers.com/showthread.php?t=1623481
after that do this
http://forum.xda-developers.com/showthread.php?t=1785672
this is hard...
thank you all, i am working on it, but i still don't understand.
Jayjay: I downloaded the SDK and followed the instructions in the guide you suggested, but my PC does not recognize the Android device.
When I try to browse for the driver software I get a Hardware Update Wizard, and then I'm up to my ass in alligators. "Choose Hardware Type" it says but none of them are accepted. There is no choice called "Android Bootloader Interface". There are 2 folders, one for i386 and one for amd64, my PC is athlon64X2 so I look in there, and there are 3 "dll"s but nothing with that name.
Anyway I thought my phone was already rooted, why do I have to root it again? Must it be done in a certain way so that you can be sure that it was done properly?
I will keep trying, but this is bloody hard work.
are you sure?
raducux said:
Install rom manager... the cwm 6.0.1.0 applies the ota.
Make sure you tick ota survival in superuser and after the ota cwm will ask you is you want to keep the stock recovery for next boot or keep the cwm.
Then it asks you to fix root rightz..select fix . And now you got the 4.1.1 rooted by ota
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
I have read this on another forum:
Please note that you cannot flash clockwork on Samsung Phones using ADB, or ROM Manager (you'll hard brick the device). If there is a version of clockwork (specific to that particular Samsung device) it must be flashed using Odin.
So what do I believe?
monkey shoulder said:
Jayjay: I downloaded the SDK and followed the instructions in the guide you suggested, but my PC does not recognize the Android device.
When I try to browse for the driver software I get a Hardware Update Wizard, and then I'm up to my ass in alligators. "Choose Hardware Type" it says but none of them are accepted. There is no choice called "Android Bootloader Interface". There are 2 folders, one for i386 and one for amd64, my PC is athlon64X2 so I look in there, and there are 3 "dll"s but nothing with that name.
Anyway I thought my phone was already rooted, why do I have to root it again? Must it be done in a certain way so that you can be sure that it was done properly?
I will keep trying, but this is bloody hard work.
Click to expand...
Click to collapse
So you didn't get through part 1 in this? http://forum.xda-developers.com/showthread.php?t=895545
This can help you with the drivers. Install and run.
http://junefabrics.com/android/download.php
I heard people using this, I've never tried it http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/ or http://forum.xda-developers.com/showthread.php?p=23573589
You are rooted but your bootloader is locked so you have to unlock it to reflash a rom, including 4.1.1. You can't do the OTA in the current state of your phone. http://forum.xda-developers.com/showpost.php?p=29519097&postcount=11
More info http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
Hope this helps.
monkey shoulder said:
I have read this on another forum:
Please note that you cannot flash clockwork on Samsung Phones using ADB, or ROM Manager (you'll hard brick the device). If there is a version of clockwork (specific to that particular Samsung device) it must be flashed using Odin.
So what do I believe?
Click to expand...
Click to collapse
clockworkmod website. Pick nexus s http://www.clockworkmod.com/rommanager/
Getting tired...
jayjay3333 said:
So you didn't get through part 1 in this? http://forum.xda-developers.com/showthread.php?t=895545
This can help you with the drivers. Install and run.
http://junefabrics.com/android/download.php
I heard people using this, I've never tried it http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/ or http://forum.xda-developers.com/showthread.php?p=23573589
You are rooted but your bootloader is locked so you have to unlock it to reflash a rom, including 4.1.1. You can't do the OTA in the current state of your phone. http://forum.xda-developers.com/showpost.php?p=29519097&postcount=11
More info http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
Hope this helps.
clockworkmod website. Pick nexus s http://www.clockworkmod.com/rommanager/
Click to expand...
Click to collapse
When I plug the phone into the PC a "New Hardware Wizard" starts. I guided it to the "\\android-sdk\extras\google\usbdriver" folder and it "cannot install this hardware because it cannot find any software". The folder "USB driver" has a file called "android_winusb.inf", which appears to contain information specifically relating to the Nexus S, but the sub folders contain .dlls which are not recognized by the wizard, and there is no file called "Android Bootloader Interface" anywhere.
So I tried again. This time I let the wizard search for software, and it found an Acer USB driver which it installed. But when I connect the phone it is still not recognised, and the wizard wants to run again.
Ok this time I try the PDA net software that JayJay recommends. I'm not sure what it's supposed to do, but when I try to connect my phone the PC says "Error 2DAnet driver is either not installed or must be reset, try to reboot you computer", which I do, with no improvement. Oh and a pop up from the systray sez "Broadband error 13"
I am assuming that when the phone is "recognized", I will have full access to the file system. At the moment, when I connect, it calls the phone " usb mass storage device, drive J " and is treating it as if it is a memory stick. I have successfully backed up photos, music and downloaded files to the PC. One of the things I have been trying to do is get at the wallpaper photo which I have read is in "data\data\com.android.settings\files\wallpaper.jpg" but I cannot find such a folder on my phone, so I assume it must be one of those things you get to see when you've got this "android debug bridge " thing.
I am getting tired now I have been at this for hours.
Tomorrow I will try the "ROM Manager"
Goodnight.
Progress
So I download the ROM Manager. On the first Run the screen goes black and stays black. A great start. I reboot and get Rom manager. It is trying to sell me google chrome. No thank you I want Android 4.1.
Rom manager tells me that my ROM "is not set up to receive over the air updates - please contact ROM developer." Who might that be? Is it called Herring? I have no idea who supplied the 4.0.4 ROM for this device. I try to backup the current ROM and Rom manager wants to reflash the ClockworkMod recovery.
Now I have discovered that I have CWM installed already. (It must have been there for the previous owner to have installed ICS.) I have CWM 5.0.2.0.
Still, best to have the latest version...and so I flash the CWM.
This fails 3 times and I have to reboot each time. I then try updating Superuser to the latest version. This also fails and hangs the phone, just a screen saying "downloading manifest". No sign of progress, no status bar, no rotating thingy. Eventually I reboot and try again. ( I am getting confident about this reboot game, I've had to do it lot's of times and so far it hasn't let me down, and brings me back to a working phone.)
When Superuser has finally settled down to v3.1.3, su binary v3.1.1 I have another shot at flashing CWM from ROM manager. Yeah! This time it sticks!
I now have CWM 6.0.1.0
So I back up my ROM...this seems ok apart from a message "no sd-ext found"... but I don't know what that means so I ignore it.
Now I try applying the 4.1.1 update. All looks good for a while with a little android with a dodecahedran or something in its belly. Then..clunk!
The little android is on it's back with it's legs in the air. There is a report that I send to rommanager. It is long, (would you like me to Post it?)
basically it says:
" can't open /dev/tty0: no such file or directory"
"unable to get recovery.fstab info for datadata fstab generation"
"failed to verify whole file signature"
"failed to open /sys/class/android-usb/android0/state: no such file or directory" - this over and over again...
Now I think I have a BIG problem.
I get the feeling that something is corrupted and there are bits missng from my file structure. This would explain why I could not find a "data/data" directory and a whole lot else.
Actually beginning to enjoy this, I may end up with £150 paperweight, but I am learning a lot about code. Like when I got the SDK ADB installed and typed help then found that I couldn't send the output on the Command Line to the printer so I had to look it up on Wikipedia...
I am still learning. I think I need to know where to get the true Google Android 4.1.1 from if I cant get it over the air.
I have read about a thing called Nexus Root Toolkit by a chap called Wug fresh or something, I am not unfamiliar with DOS but my command line skills are a bit rusty.
I started with Algol 60 you know.
Goodnight
Close but no cigar...
OK. I have backed up my rom, using Titanium Backup.
I have "unlocked" my bootloader using the downloaded Android SDK ADB fastboot.exe ( It's in "platform tools" now, not "tools")
I have CWM 6.0.1.0 , Superuser 3.1.3 with OTA survival ticked.
Now all I have to do is wait until the OTA upgrade is offered again. ( It seems to come round randomly, every few days.)
Ssh! wait.. Yes! After leaving the phone overnight, the upgrade was waiting for me in the morning. I tap install..
...and fail again.!
This time its:
E: failed to verify whole file signature
E: error in /cache/9ZGgDXDi.zip (status 7)
installation aborted.
Why do you guys make it sound so easy?
I clear my cache ( if there is an error in it, it makes sense to clear it.)
I'll try again tomorrow.
monkey shoulder said:
OK. I have backed up my rom, using Titanium Backup.
I have "unlocked" my bootloader using the downloaded Android SDK ADB fastboot.exe ( It's in "platform tools" now, not "tools")
I have CWM 6.0.1.0 , Superuser 3.1.3 with OTA survival ticked.
Now all I have to do is wait until the OTA upgrade is offered again. ( It seems to come round randomly, every few days.)
Ssh! wait.. Yes! After leaving the phone overnight, the upgrade was waiting for me in the morning. I tap install..
...and fail again.!
This time its:
E: failed to verify whole file signature
E: error in /cache/9ZGgDXDi.zip (status 7)
installation aborted.
Why do you guys make it sound so easy?
I clear my cache ( if there is an error in it, it makes sense to clear it.)
I'll try again tomorrow.
Click to expand...
Click to collapse
Ok now just get the proper factory image. You are a Nexus S i9020 just check if you are a T or an A (look under the battery). Flash Android 4.1.1 (JRO03E). Follow part 1 of this guide http://forum.xda-developers.com/showthread.php?t=1785672
Then flash clockwork and super su
Stock, rooted, profit!
stick with it...
monkey shoulder said:
OK. I have backed up my rom, using Titanium Backup.
I have "unlocked" my bootloader using the downloaded Android SDK ADB fastboot.exe ( It's in "platform tools" now, not "tools")
I have CWM 6.0.1.0 , Superuser 3.1.3 with OTA survival ticked.
Now all I have to do is wait until the OTA upgrade is offered again. ( It seems to come round randomly, every few days.)
Ssh! wait.. Yes! After leaving the phone overnight, the upgrade was waiting for me in the morning. I tap install..
...and fail again.!
This time its:
E: failed to verify whole file signature
E: error in /cache/9ZGgDXDi.zip (status 7)
installation aborted.
Why do you guys make it sound so easy?
I clear my cache ( if there is an error in it, it makes sense to clear it.)
I'll try again tomorrow.
Click to expand...
Click to collapse
Its a bit confusing to begin with mate, but read and re-read the many tutorials and guides on here, take it slowly and step by step and youll get there in the end.
Youll be flashing custom ROMs before you know it! (take your time and always backup)
Is worth it. :good:
S
It is good that in the process you learnt lot of things. Now you have fastboot working and you know how use fastboot.
Now that the OTA is giving errors, the best way is to flash the Jelly Bean factory image which is available from Google. As per suggestions from
jayjay3333 said:
Ok now just get the proper factory image. You are a Nexus S i9020 just check if you are a T or an A (look under the battery). Flash Android 4.1.1 (JRO03E). Follow part 1 of this guide http://forum.xda-developers.com/showthread.php?t=1785672
Then flash clockwork and super su
Stock, rooted, profit!
Click to expand...
Click to collapse
Go to the link to download the image files first, then flash the 3 files using the fastboot commands provided. The overall process of flashing the factory images does not take more than 5 mins.
Best of luck.
nearly there...
jayjay3333 said:
Ok now just get the proper factory image. You are a Nexus S i9020 just check if you are a T or an A (look under the battery). Flash Android 4.1.1 (JRO03E). Follow part 1 of this guide http://forum.xda-developers.com/showthread.php?t=1785672
Then flash clockwork and super su
Stock, rooted, profit!
Click to expand...
Click to collapse
Ok I downloaded the jro03e file it is 191Mb
The download is a .tar file not a tar.gz It is called soju_jro03e_factory_c9f5a67d.tar. It is196,458 kb
The instructions say I should 'extract' it, using 7zip, which gives me a file with the same name but no extension! Windows identifies it as a ".file". It is now 207,410 kb.
The instructions say there is a folder inside which I should extract. No such thing is visible.
The next part of the instructions says I should modify the file names before running. Does that mean:
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
fastboot -w update image-soju_jro03e_factory_c9f5a67d.tar
Is that right? Shouldn't all those hyphens be underscores?
Is that xxkl1 or xxki1 the same or different? ( looks like a typo).
Does only the last bit change?
Ready when you are!
oops silly me...
Well it looks like I don't understand 7Zip very clearly.
After a bit of fiddling about I "extracted" the .tar file, then "extracted" the resulting file to get a folder with a bootloader image, a radio image and an image-soju-jro03e.zip
I tried to follow the XDA instructions given here http://forum.xda-developers.com/showthread.php?t=1785672
but it seems I don't understand how to use ADB fastboot either, because when I entered the commands all I got was a list of options, a sort of helpfile for the fastboot command.
I am just not comfortable with the command line, you make one mistake and you've got to enter it all again.
Anyway I decided to try the "Nexus Root Toolkit" http://www.wugfresh.com/dev/nexus-root-toolkit/
After ensuring that my drivers were OK, I pointed the toolkit at the files and executed them individually. ( There is a "flash-all.sh" , but I don't understand how to use that. )
first of all I flashed the bootloader... Success! I now have bootloader crespo i9020xxlc2.
I didn't bother with the radio, I already have radio-crespo-i9020xxki1.
So I try to flash the jro03e.zip... Damn! The toolkit cannot find my device! Funny, it was perfectly happy before the bootloader flash...maybe that has changed something. I start again, reboot everything, check drivers... yes all ok. This time the toolkit is happy and offers to install the .zip, I include a full nandroid backup and drag and drop the image-soju-jro03e.zip to the install/flash.zip box.
TWRP v2.2.0 does it's thing and after a lot of stuff happens on the phone screen I get a menu, from which I access a report that basically says: "Error flashing zip". My heart sinks...
Other attempts with different settings result in the same:
"signature verification failed"
"no MD5 file found"... etc... etc...
So I reboot again and am relieved to find that I still have a phone.But it is still 4.0.4.
Ah! but now it has the image.zip on the SD! Progress! My heart soars with new hope!
This time I use ROM Manager to install the .zip from SD... But no such luck, "installation aborted", the little green android is flat on its back again.
Rom Manager generated a recovery log. (would you like me to post it?) Basically it says:
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
Preparing to install ROM...
about to run program [/cache/dowipedalvikcache.sh] with 1 args
mount: mounting /dev/block/mtdblock4 on /cache failed: Device or resource busy
mount: can't find /sd-ext in /etc/fstab
umount: can't umount /sd-ext: Invalid argument
run_program: child exited with status 1
Installing update...
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/!ReadyToFlash/image-soju-jro03e.zip")
Have you any idea what that all means?
Will I ever get JB 4.1 on this phone?
Its beginning to look like there is something fundemental missing.
Please help!
S.
its gone quiet...
This thread doesnt seem to be getting attention anymore so I shall start a new one.
Is that ok? Its a new question "what does this recovery log tell me?", but it is still the same problem. The trouble is there are too many questions and it is very difficult to know what to ask.
I am still trying to get Android 4.1 on my phone. I have read the various instructions and tried to follow them but they did not work in the way I expected. Part of the problem is that I do not understand what I am doing. I don't understand the tools I am using.
I think it would help a great deal to see the file structure on my phone.
Is there a program that can look at that like windows explorer? Then I might be able to see what I am doing. At the moment I have no idea what is on my "SD card". The Nexus S doesnt actually have one of course, but I understand that it has 16Gb of storage that work like an SD card.
Now In the course of this project, I have "Backed up" with Rom Manager, but I don't know where that backup is, or what it is called. I did a "Nandroid backup" with the Nexus Root Toolkit but I have no idea where that is (is it on PC, or on the phone somewhere?) or what it is called. I assume it will be found automatically by the software when it needs to restore it. I have not backed up with "Titanium Backup" beause I am not sure how to do it. When I select "Backup/Restore" it displays a long list of files, some in red some in green, which say they are not backed up yet. Which ones do I select? All of them? I have no idea.There are so many options in the menus that I am terrified of Titanium, and don't know where to start, and it is going to take days to read the helpfiles. Is Titanium saying they are not backed up because it didn't back them up, or because it can't recognise the backups that were made with Rom Manager? If I backup everything with Titanium, is it going to make backups of the backups that another program made?
I'd like to be sure that I have just one good copy of the backup, that I havent filled my memory with useless junk.
S
Hello, I have a Motorola Defy which i have rooted and installed clockworkmod on it. I tried to install Cyanogen mod 7.1 from the website. The phone got to the boot screen where it continued to cycle through it thing and nothing more. I restarted the phone and now it gets stuck at the first screen where its says "google". I tried to enter recovery again (power + volume down) and clockworkmod is completely gone. I want to go back to the stock OS so it atleast works again. Ive tried using the update.zip option in the stock recovery mode but I keep getting an error "failed to verify whole-file signature" when using a signed copy of cyanogen mod. I also tried putting my backup in a zip with the same error. Ive even tried formatting my sd card. What do i do?
I was more or less where you are around June or so. I'm no expert by any means, but perhaps I can help. If memory serves I used a program called RSD Lite to flash it back to the stock unlocked rom I got from the "bl7 finally rooted" thread - if you unlocked a different way, I'd try to find your original rom.
Once you get to where you understand how to get back to stock it makes the whole thing a lot less scary, or it did for me. Once you get back up and running, try flashing Whiterabbit. I didn't have luck getting anything else to run, but that one worked the first time I tried it, and I'm very happy I persevered. Miles better than the stock OS.
Marvelicious75 said:
I was more or less where you are around June or so. I'm no expert by any means, but perhaps I can help. If memory serves I used a program called RSD Lite to flash it back to the stock unlocked rom I got from the "bl7 finally rooted" thread - if you unlocked a dirrerent way, I'd try to find your original rom.
Once you get to where you understand how to get back to stock it makes the whole thing a lot less scary, or it did for me. Once you get back up and running, try flashing Whiterabbit. I didn't have luck getting anything else to run, but that one worked the first time I tried it, and I'm very happy I persevered. Miles better than the stock OS.
Click to expand...
Click to collapse
I cant use the program as my phone doesnt get detected when connected to my pc.
OK, lets start with the basics, if I can remember it right... Have you used RSD Lite successfully before this? Drivers installed? Using bootloader mode? If any of this is unfamiliar go hit the beginner's thread - if you have done all this you may be beyond my help and in need of someone a bit more experienced.
Marvelicious75 said:
OK, lets start with the basics, if I can remember it right... Have you used RSD Lite successfully before this? Drivers installed? Using bootloader mode? If any of this is unfamiliar go hit the beginner's thread - if you have done all this you may be beyond my help and in need of someone a bit more experienced.
Click to expand...
Click to collapse
I fixed it, there were a different set of buttons to hold to get into boot loader. The default recovery was not over written as i thought (happened to all my other phones). Thank you very much for you help. It has been very much appreciated.
Glad to hear it.
Hello, guys!
Basically, my rooted device apparently got a virus (not sure), so I did a factory reset. Now I can't get past the setup wizard because it stops unexpectedly. I tried using a custom ROM (I'm on 2.3), and it fails the signature verification.
So, the only approach for me to take seems to be installing CWM or ROM manager or anything else directly into my phone via my PC. Don't know how to do that, though. I can't access or do anything in my phone, so whatever needs to be done needs to be done via my PC, probably.
I'm using an Alcatel One Touch 985.
Thanks in advance!
Note: Installing a fresh copy of the setup wizard would be the easiest fix of all, or even the stock Android ROM. Once I get my phone working in its basic form, everything else becomes much easier to do.
If your phone still boots in either recovery or download mode, then its not bricked
If you have a custom recovery, you can flash your custom rom. If you don't, you can flash a stock ROM
Hope this helps
Basically, my rooted device apparently got a virus (not sure), so I did a factory reset. Now I can't get past the setup wizard because it stops unexpectedly. I tried using a custom ROM (I'm on 2.3), and it fails the signature verification.
Click to expand...
Click to collapse
what that is its most likely the rom you downloaded is for a different phone, are you sure it was your phone specificly? check model no. if not theres a option in CWM to uncheck signature verification and it will sorta force flash what you wanted to flash.
If your phone still boots in either recovery or download mode, then its not bricked
If you have a custom recovery, you can flash your custom rom. If you don't, you can flash a stock ROM
Hope this helps
Click to expand...
Click to collapse
Read the Question before posting stupid Answers, this shows that you didnt even read it...
I can still enter recovery mode, yes.
This all happened while using the ROM the phone came with.
I've tried with what seems to be the only compatible ROM for my phone, and also with other 2.3 ROMs. The problem regarding the ROM issue seems to be that the phone's boot loader isn't unlocked.
I know CWM can fix the signature problem, but how do I get it into the phone in the first place? That's the real issue.
Edit: I've tried unblocking the boot loader with the help of a tutorial online, but I believe I'm missing a step. Ideally this fix should be attempted after I know for sure there's no way to simply install an apk directly into the phone through my PC.
Klowdz said:
I can still enter recovery mode, yes.
This all happened while using the ROM the phone came with.
I've tried with what seems to be the only compatible ROM for my phone, and also with other 2.3 ROMs. The problem regarding the ROM issue seems to be that the phone's boot loader isn't unlocked.
I know CWM can fix the signature problem, but how do I get it into the phone in the first place? That's the real issue.
Edit: I've tried unblocking the boot loader with the help of a tutorial online, but I believe I'm missing a step. Ideally this fix should be attempted after I know for sure there's no way to simply install an apk directly into the phone through my PC.
Click to expand...
Click to collapse
have you tired factory reseting it again? the setup wizard crash is really werid at a stock rom.
I have. Same result.
Perhaps I deleted some file needed for the wizard to function properly.
I don't mind flashing a new ROM into the phone, or do whatever else in order for it to work properly.
Klowdz said:
Hello, guys!
Basically, my rooted device apparently got a virus (not sure), so I did a factory reset. Now I can't get past the setup wizard because it stops unexpectedly. I tried using a custom ROM (I'm on 2.3), and it fails the signature verification.
So, the only approach for me to take seems to be installing CWM or ROM manager or anything else directly into my phone via my PC. Don't know how to do that, though. I can't access or do anything in my phone, so whatever needs to be done needs to be done via my PC, probably.
I'm using an Alcatel One Touch 985.
Thanks in advance!
Note: Installing a fresh copy of the setup wizard would be the easiest fix of all, or even the stock Android ROM. Once I get my phone working in its basic form, everything else becomes much easier to do.
Click to expand...
Click to collapse
Try installing the ROM again, doing the correct wipe. After installing the ROM give the fix permission option.
In what novel way should I do that? I've tried the regular way, as mentioned above, and nothing.
Klowdz said:
In what novel way should I do that? I've tried the regular way, as mentioned above, and nothing.
Click to expand...
Click to collapse
If phone boots, is rooted and setup wizard stops just remove setup wizard app via adb.
Code:
adb shell rm /system/app/<name-of-setup-wizard-app>.apk
Cheers,
AJ
How do I do that? I have the SDK and everything installed, but that's it.
Klowdz said:
How do I do that? I have the SDK and everything installed, but that's it.
Click to expand...
Click to collapse
Following steps are for Windows PC
U need to find a file called adb in the folder of SDK
I use an older version of SDK and it's in folder named 'platform-tools'
Open the folder which contains this file
Then u need to open command prompt window there
( Do that by holding shift while right clicking in the folder then select 'open command window here' option)
Then u can type the following code
in the window.
Abhinav2 said:
adb shell rm /system/app/<name of setup wizard>.apk
Click to expand...
Click to collapse
Sent from my GT-I9000
It says it's a read-only file system.
Maybe It only works if your phone is rooted
If u r rooted U can try adding su command before it
su adb shell rm /system/app/<name of setup wizard>.apk
.
Sent from my GT-I9000
"Su" isn't recognized, but I clearly have it since whenever I try to access adb shell it asks me for permission (not for this task, but for another).
Wouldn't it be simpler to just install the setup wizard again? The problem is where to find that .apk.