Database Info

[Q] In need of aid :(

Hi
Bourght a nexus s a few days ago. Today i tried to root the phone using a guide from youtube, if you search for "root nexus s" and look for the user named "Zedomax", thats the one i tried to follow.
First i unlocked it.
next thing was to:
fastboot flash boot recovery clockwork.img (shortend the name to help my self)
last thing:
fastboot flash boot rootboot.img
After this was done my phone is unable to reboot again, it just stops at a google logo with a lock under it. And at that point im unable to do anything. Only thing that works is removing the battery. Think i have killed it
Any ideas to what i could do? is it possible for me to save it yet?
best regards,
Fonain

try to use the pc software to repair it or to reinstall android.. there is no problem..

pc software? could you please tell me what software are you talking about, maybe a link to where i can download it? And do you by chance know how to reinstall android?
any help is highly appreciated
Best regards,
fonain
edit: at work atm, so might not be able to answer right away

Odin.
http://forum.xda-developers.com/showthread.php?t=94795
I have yet to use it on my NS but i used it regularly on my vibrant. You will need to get into download mode for it to work.

your link doesnt work

does anyone know where i can find the original files for nexus s so i can use em in fastboot and make my phone work again?

fonain said:
does anyone know where i can find the original files for nexus s so i can use em in fastboot and make my phone work again?
Click to expand...
Click to collapse
which phone model do you have?
i9020 or i9023 ?

Bootloader version is I9020XXKA3
Baseband version is I9020XXKB1
dunno if those version names have been changed while i have been tampering with my phone, if not its the I9020

that looks good
if it's really a 9020 then you can use the unlocking + rooting guide for the 9020 in the general section
once you get CWR installed, you can flash to any ROM you like

Thanks ill try look deeper into that, and see if that will solve my problem.
but it is already unlocked and partly rooted...i think.
have used a clockwork img and rootboot img, and after that my phone couldnt start up again.

fonain said:
Thanks ill try look deeper into that, and see if that will solve my problem.
but it is already unlocked and partly rooted...i think.
have used a clockwork img and rootboot img, and after that my phone couldnt start up again.
Click to expand...
Click to collapse
those files are wrong use the mirror recovery image on the i9020 rooting topic in general http://forum.xda-developers.com/showthread.php?t=895545

Think i should have used that guide instead of the one i have been using the first time... looks great step by step!
But....
i still have the problem where my phone just stops loading.
1: unlocked it
2: typed: fastboot flash recovery recovery.img
3: finished at 1.132 sec (no problems so far)
4: reboot my phone, then it stops.
and it stop when showing this screen.
http://i53.tinypic.com/m74byg.jpg with a lock at the bottom which is unlocked.
And it just stops there, waited for several minutes as i have seen that the startup could take up to 2 mins after tampering with the nexus s.
get to the point in the guide where it tells you to download superuser.
Hope you can see if i have done something wrong
best regards,
Fonain
EDIT: oh yes, forgot to mention that the 2 touch buttons to the left on my SNS lights up. First one glowes for a sec or two, then it turns off again. The second stays on all the time.

repeat the fastboot flash recovery recovery.img one more time
after that is done, boot into the CW Recovery
you know hold up and power
then select mount USB
then copy over a stock nandroid backup for 2.3.3 rooted
after that unmount the usb
and select the option to restore rom from backup
and choose the folder that you unzipped into your mounted SD

3 words...
you are awesome!
thanks alot!!
Best regards,
Fonain

Help with ROM load

I bricked my xoom trying to fix the uastring. For some reason cw doesnt recognize my sd card so i cant just reflash, ive tried it with a different sdcard so it must be something with cw.. anyway, how should i proceed from this point?

Adb push the old framework-res.apk back to system/framework. If you didn't back it up download a rom extract the file then push it.
Oh and to edit the framework-res.apk i had to replace the res folder and the resources.xx file then it worked.
Sent from my Xoom using XDA Premium App

thanks for the help, but that was like speaking greek to my...lol seeriously, i know just enough to get myself into troulble... is there a step by step anywhere?

Try this
http://www.lmgtfy.com/?q=xoom+cwm+not+recognized+sd

Moved to QA since this is a Question.

wardo5757 said:
thanks for the help, but that was like speaking greek to my...lol seeriously, i know just enough to get myself into troulble... is there a step by step anywhere?
Click to expand...
Click to collapse
OK, you unfortunately updated your recovery to the dreaded 4.0.0.x in CWM and it doesn't see your sd card. You need to install a good version of the recovery (specifically 3.2.0.0) that does read it. Are you stuck at the dual core screen, or can you get into any recovery? You sound like you know enough to get out of this jam since you rooted. Now that you know what the problem is, I'm sure you can resolve it. Xooms are actually pretty hard to really brick. I've gotten myself into and out of some very hairy situations.

Thanks for all the help! Unfortunately I'm at my inlaws tonight, when I get back home tomorrow I will use your guidance...... Yes, I am stuck at the dual core screen but I can still get into cwm. Thanks again, I can't wait to get it fixed, I am having to type this on my wife's iPad, yes, it's killing me!

wardo5757 said:
Thanks for all the help! Unfortunately I'm at my inlaws tonight, when I get back home tomorrow I will use your guidance...... Yes, I am stuck at the dual core screen but I can still get into cwm. Thanks again, I can't wait to get it fixed, I am having to type this on my wife's iPad, yes, it's killing me!
Click to expand...
Click to collapse
Let us know if and how you get it worked out.

****............. i did it this time guys... i now have " failed to boot LNX 0x0004
starting RSD mode 2" is it done?

i think im going to try the SBF, what do you guys think?

wardo5757 said:
****............. i did it this time guys... i now have " failed to boot LNX 0x0004
starting RSD mode 2" is it done?
Click to expand...
Click to collapse
Boot your xoom into fastboot mode manually. To do this hold the volume up and power button until the xoom turns off. As soon as you see the moto logo start tapping the volume down button. in the upper left corner you should get options, choose fastboot. In Fastboot mode try running "fastboot devices" from command promt on PC first to see if the xoom is recognized. If it is, you can be saved. From here try "fastboot oem unlock", you should then see intructions to follow on the xoom screen. If when you reboot you get the same issue, get into fastboot again and flash the original stock moto images. Good luck.

jase33 said:
Boot your xoom into fastboot mode manually. To do this hold the volume up and power button until the xoom turns off. As soon as you see the moto logo start tapping the volume down button. in the upper left corner you should get options, choose fastboot. In Fastboot mode try running "fastboot devices" from command promt on PC first to see if the xoom is recognized. If it is, you can be saved. From here try "fastboot oem unlock", you should then see intructions to follow on the xoom screen. If when you reboot you get the same issue, get into fastboot again and flash the original stock moto images. Good luck.
Click to expand...
Click to collapse
it will not go into options when doing that sequence, goes to that error code. sbf using rsd lite didnt work either....

forget that last post! ok, i got it into "fastboot protocal support" what next?

for some reason, the comand promt in sdk isnt accepting any keys. i have no idea whats going on.....
just a progress update, by using the one click root method i was able to get back into recovery, unfortunately its the 4.0.0.4, but im getting closer. now if i can figure out whats going on the sdk, TE will not take any input

ok,ive gotten sdk sorted out. i have been using this guide (starting at step 4), file on my pc are in the right place but i cannot seem to get the proper cwm flashed. is this the right command, except for the file location? I put the .img file in the root of c:

SHE"S BACK!!! I was having probleams flashing becuse the c: in that command line psoted was in the worng place. once i got flashed back to 3.2 cwm it was a breeze ofcourse.
Thanks for all the help guys, I know its a pain helping a dumb ass,,, thanks again!

help.

i just installed pacman rom using clockworkmod recovery something..

fastboot flash boot boot.img.
Google that, instead of spamming threads in all the forums. This is the most commonly occurring beginner error, it's stated multiple times in multiple places, and still people keep asking instead of reading.
If it's not your case - look at "non-Sony screen" thread.

Jack_R1 said:
fastboot flash boot boot.img.
Google the damn thing, instead of spamming threads in all the forums.
Click to expand...
Click to collapse
m extremely sorry..
but i have been trying since 2 hrs..
still could not find a solution..
pleae help!

jigi1993 said:
m extremely sorry..
but i have been trying since 2 hrs..
still could not find a solution..
pleae help!
Click to expand...
Click to collapse
please guys help..
the bloody boot.img is not supportted by winzip..
'fastboot' is not recognized as
operable program or batch file.
error

Jack_R1 said:
fastboot flash boot boot.img.
Google that, instead of spamming threads in all the forums. This is the most commonly occurring beginner error, it's stated multiple times in multiple places, and still people keep asking instead of reading.
If it's not your case - look at "non-Sony screen" thread.
Click to expand...
Click to collapse
jigi1993 said:
please guys help..
the bloody boot.img is not supportted by winzip..
'fastboot' is not recognized as
operable program or batch file.
error
Click to expand...
Click to collapse
Did you do what Jack said and GOOGLE IT????? Go away and put some effort in for yourself - it will be much better for you to understand WHAT and WHY you need to do things - or next time you will brick your phone beyond recovery.

SimonTS said:
Did you do what Jack said and GOOGLE IT????? Go away and put some effort in for yourself - it will be much better for you to understand WHAT and WHY you need to do things - or next time you will brick your phone beyond recovery.
Click to expand...
Click to collapse
Sir m damn serious..
i hve been googling in around 4 hrs now..
i did my best but i cant now..
please provide an easy solution..
the boot image error comes in..
i cant extract that file .

Here you go

SimonTS said:
Here you go
Click to expand...
Click to collapse
kk.

So you've installed ADB then?

SimonTS said:
So you've installed ADB then?
Click to expand...
Click to collapse
i downloaded pacman rom.
copied it into root of sd.
wiped data and installed it through clockmod recovery .!
it was installed properly but after reboot it stuck on htc white screen..

:banghead:

teadrinker said:
:banghead:
Click to expand...
Click to collapse
I couldn't agree more - I give up on this guy, if he can't even deal with what I asked then there is no hope for him.

Ok I don't know why I'm doing this but your answer is in this thread
http://forum.xda-developers.com/showthread.php?t=1525100
[Guide] How to root, install EXT4 recovery and custom ROM on HBOOT 2.00.0002
Everyone has a right to be stupid. Some just abuse the privilege

jugg1es said:
Ok I don't know why I'm doing this but your answer is in this thread
http://forum.xda-developers.com/showthread.php?t=1525100
[Guide] How to root, install EXT4 recovery and custom ROM on HBOOT 2.00.0002
Everyone has a right to be stupid. Some just abuse the privilege
Click to expand...
Click to collapse
Because we are too nice...
@op cd ( http://en.wikipedia.org/wiki/Cd_(command) ) in the directory where your fastboot and adb in located ( path-to/platform-tools) and fastboot commands should be working.

Oh c'mon guys don't be so rude. You've been noobs too.
To return in topic:
1) you have the clockwork mod recovery, so I'm assuming that you already have unlocked the boot loader but you still S-ON ( you can check it by powering up the phone by pressing TOGETHER the volume down AND the power button). But i may ask you to verify that you have installed on your PC at least ADB and FASTBOOT? If you're not, please install them, otherwise you won't be able to get your phone work.
2) now, you say that you have flashed the pacman ROM but you are stuck on the HTC logo. Don't panic. It is a common issue, i have done it a lot of times. Just check from adb if it can see you device (you have to plug in the phone to the computer via your recharge cable). If it sees the phone it is quite simple to return to the boot loader. Simply open a terminal on your pc, navigate on the folder in which you have saved adb and write "adb reboot bootloader". This will bring you to the bootloader screen. Check now if there is written "FASTBOOT USB". If not and it is written HBOOT USB navigate with the volume keys on fastboot. This should bring you to the fastboot usb.
Now double click on the .zip containing the pacman ROM you've installed. Extract ONLY the boot.img and place it in the same directory in which you've placed fastboot. Now in the terminal of you PC write "fastboot flash boot boot.img" and then reboot the phone. This should solve your issue.
If the adb doesn't see you phone you have to pull out the battery, WAIT at least 30 seconds, replace it, and then press TOGETHER volume down and power button to enter into bootloader. From there follow the step that i wrote you previously and you'll be good to go!
Sent from my Desire S using xda app-developers app

Jedioscuro said:
Oh c'mon guys don't be so rude. You've been noobs too.
To return in topic:
1) you have the clockwork mod recovery, so I'm assuming that you already have unlocked the boot loader but you still S-ON ( you can check it by powering up the phone by pressing TOGETHER the volume down AND the power button). But i may ask you to verify that you have installed on your PC at least ADB and FASTBOOT? If you're not, please install them, otherwise you won't be able to get your phone work.
2) now, you say that you have flashed the pacman ROM but you are stuck on the HTC logo. Don't panic. It is a common issue, i have done it a lot of times. Just check from adb if it can see you device (you have to plug in the phone to the computer via your recharge cable). If it sees the phone it is quite simple to return to the boot loader. Simply open a terminal on your pc, navigate on the folder in which you have saved adb and write "adb reboot bootloader". This will bring you to the bootloader screen. Check now if there is written "FASTBOOT USB". If not and it is written HBOOT USB navigate with the volume keys on fastboot. This should bring you to the fastboot usb.
Now double click on the .zip containing the pacman ROM you've installed. Extract ONLY the boot.img and place it in the same directory in which you've placed fastboot. Now in the terminal of you PC write "fastboot flash boot boot.img" and then reboot the phone. This should solve your issue.
If the adb doesn't see you phone you have to pull out the battery, WAIT at least 30 seconds, replace it, and then press TOGETHER volume down and power button to enter into bootloader. From there follow the step that i wrote you previously and you'll be good to go!
Sent from my Desire S using xda app-developers app
Click to expand...
Click to collapse
Hey, i wasn't rude. I gave e a thread that is a good starting point to solve his issue without talking him through it
A word to the wise ain't necessary -- it's the stupid ones that need the advice.
Bill Cosby

jugg1es said:
Hey, i wasn't rude. I gave e a thread that is a good starting point to solve his issue without talking him through it
Click to expand...
Click to collapse
^^^^ This ^^^^ There is a HUGE difference between helping someone when they need help and helping someone when they are just being too lazy to actually read and find things out themselves.
I see it as no different to when I need tech-support from one of my equipment suppliers. If I call them up with a genuine problem they will help me, but if I phone them and say "Where do I plug the keys in?" or "I've turned the kit on but didn't bother reading the instructions first, now it's broken" - what do you think their reply to me will be?

SimonTS said:
^^^^ This ^^^^ There is a HUGE difference between helping someone when they need help and helping someone when they are just being too lazy to actually read and find things out themselves.
I see it as no different to when I need tech-support from one of my equipment suppliers. If I call them up with a genuine problem they will help me, but if I phone them and say "Where do I plug the keys in?" or "I've turned the kit on but didn't bother reading the instructions first, now it's broken" - what do you think their reply to me will be?
Click to expand...
Click to collapse
Yeah, you're right. But from the disperation of the guy It seemed to me pointless to leave him with a non-functioning phone without any advise. After all this is a forum plenty of people that know how to do practically everything with an android device, but I don't think that everyone have started from a solid programming base or a perfect hardware knowledge.
Regarding me, I have looked into this forum a couple of months BEFORE even try to unlock my phone and flashing something other than the horrible desire's gingerbread stock rom, but I understand the people who wants to try something new, even if they are not so expert.
For the next time, don't worry I'll be mercyless

I'm always ready to help where i can but. It seems like the op followed half a guide then just assumed it would work, i must of read all the guides until my head hurt, and most of my first posts were silly questions already posted. I learnt far more about my phone from searching than i think i could have from my first posts
A word to the wise ain't necessary -- it's the stupid ones that need the advice.
Bill Cosby

He would have avoided all the pain if he used the boot img flashing software
Sent from my Desire S using xda premium

[Q] Sudden Bootlooping! Please HELP!!!

Hi, guys! Signed up just to ask this since everyone on here seems helpful. Long story short, my digitizer got damaged, so I replaced it today. First time doing something like that, but I was EXTREMELY careful and followed a repair guide on YouTube to the dot! Phone is currently (or possibly WAS) running CM11, Android 4.4 BEAUTIFULLY! No problems whatsoever before the damage occurred.
Got the piece replaced today, turned the phone on and it started bootlooping :crying: I don't know why it started, so I opened it up again, checked every single connection and they're all good. No damaged ribbon cables, nothing. Still looping....Flashed back to stock ICS with RSD 6.1.5, still looping....Reflashed CM11, still doin' it.
I cannot for the life of my figure out what's going on. I have CWM Recovery 6.0.1.2 on it right now and got an error log to show on the screen. Here's what it says, word for word:
CWM Based Recovery v6.0.1.2
ro.hardware=gcom
ro.revision=33456
ro.emmc=1
ini.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
i: Checking for extendedcommand...
i: Skipping execution of extendedcommand. file not found...
i: Can't partition non-vfat: datamedia
i: Can't partition unsafe device: /dev/black/mmcblk1p1
i: Can't format unknown volume: /emmc
So, that's everything it says on the screen in the exact order, spacing and lettering. Does any of this mean anything to anybody? I don't know what to make of it....I'm not real into this kinda thing, other then being able to know how to flash new ROMS and root my phone. I would reflash the stock firmware, try and relock the bootloader and send it in for repair, but I know they'll know I was into it. If someone could PLEASE help me, I'd GREATLY appreciate it!

I didn't see you mention it...
Did you factory reset in recovery?

arrrghhh said:
I didn't see you mention it...
Did you factory reset in recovery?
Click to expand...
Click to collapse
Yes, a few times. Also did Dalvik
EDIT: I just found this, but I'm not sure if it's what I'm looking for: http://forum.xda-developers.com/showthread.php?t=2295643
I noticed it has emmc files in it. Could it help? They mention you need TWRP, but I can't use it. The touchscreen is still unresponsive.

StarlitSnowWolf said:
Yes, a few times. Also did Dalvik
Click to expand...
Click to collapse
Hm. You might have to RSD back to stock

arrrghhh said:
Hm. You might have to RSD back to stock
Click to expand...
Click to collapse
I mentioned in my first post I flashed stock ICS with RSD, but still no change

StarlitSnowWolf said:
I mentioned in my first post I flashed stock ICS with RSD, but still no change
Click to expand...
Click to collapse
Was the flash successful? Did you try JB? Do you have any logs? Does adb start up even?

arrrghhh said:
Was the flash successful? Did you try JB? Do you have any logs? Does adb start up even?
Click to expand...
Click to collapse
Flash seemed successful, currently downloading 4.1.2 stock ROM to flash, only log I know of is the one I described in first post, and I'm not sure what you mean by the ADB. Fastboot works

StarlitSnowWolf said:
Flash seemed successful, currently downloading 4.1.2 stock ROM to flash, only log I know of is the one I described in first post, and I'm not sure what you mean by the ADB. Fastboot works
Click to expand...
Click to collapse
When your phone is "bootlooping" see if the computer can "see" the phone - adb devices typically.

arrrghhh said:
When your phone is "bootlooping" see if the computer can "see" the phone - adb devices typically.
Click to expand...
Click to collapse
How would one do that? The computer makes it "ding" sound like it does when a device is connected to a USB port and RSD Lite will show it if it's in fastboot mode

StarlitSnowWolf said:
How would one do that? The computer makes it "ding" sound like it does when a device is connected to a USB port and RSD Lite will show it if it's in fastboot mode
Click to expand...
Click to collapse
Just like fastboot devices, adb devices from command prompt.

arrrghhh said:
Just like fastboot devices, adb devices from command prompt.
Click to expand...
Click to collapse
I'm pretty sure the ADB works. I'm able to flash recoveries with it and do the "fastboot devices" and it shows up

StarlitSnowWolf said:
I'm pretty sure the ADB works. I'm able to flash recoveries with it and do the "fastboot devices" and it shows up
Click to expand...
Click to collapse
Then use adb to pull logs when you say the device is booting.......

So, how do I do that? I don't know how to pull logs during boot, or do I do it in fastboot mode?

Bump....I left it on the charger all night long and at some point, it booted into Android, but I wasn't able to do anything. Screen was on "Hands Free Activation" and said something about a failure ota_apn. No touch response whatsoever, so I powered it back off and it's boot looping again. Can someone PLEASE help me!?!? I posted a log for CWM when I had it installed, so does any of it mean anything!?

StarlitSnowWolf said:
So, how do I do that? I don't know how to pull logs during boot, or do I do it in fastboot mode?
Click to expand...
Click to collapse
adb logcat

So, when would I want to run that? In fastboot or while the phone is trying to boot?

StarlitSnowWolf said:
So, when would I want to run that? In fastboot or while the phone is trying to boot?
Click to expand...
Click to collapse
While the phone is trying to boot... I need a log from the bootloop failure.

arrrghhh said:
While the phone is trying to boot... I need a log from the bootloop failure.
Click to expand...
Click to collapse
I just got home from dropping it off at a repair shop. If I'd known about getting the log sooner, I would've.

[Q] Lg g3 hard bricked! Flash tool failed

Hi everybody, i was updating my rooted lg phone to the latest ota (bad idea, i know). Well, it bricked. i can get into recovery mode and download mode. I used lg flash tools and the results are : "Download Fails" and then " Can't change to DL mode". What is going on! . Am i out of a phone that i got a weeks ago or is their hope? Thanks in advance any advice is welcome!

nty123 said:
Hi everybody, i was updating my rooted lg phone to the latest ota (bad idea, i know). Well, it bricked. i can get into recovery mode and download mode. I used lg flash tools and the results are : "Download Fails" and then " Can't change to DL mode". What is going on! . Am i out of a phone that i got a weeks ago or is their hope? Thanks in advance any advice is welcome!
Click to expand...
Click to collapse
stock recovery or TWRP?
any way here is what i think you're searching for
http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508

i was trying again with the flash tool on a different computer and it got significantly farther this time, to 94%. Now when i connect it it goes to the blue screen like it normally should with a number 2 showing and its just frozen there. So i do not know if i have twrp anymore, any advice?

nty123 said:
i was trying again with the flash tool on a different computer and it got significantly farther this time, to 94%. Now when i connect it it goes to the blue screen like it normally should with a number 2 showing and its just frozen there. So i do not know if i have twrp anymore, any advice?
Click to expand...
Click to collapse
you didnt disconnect the phone when it rebooted did you

Got it working, Thanks everybody.

nty123 said:
Got it working, Thanks everybody.
Click to expand...
Click to collapse
Do you mind posting what you did that was able to work? I have to wait to find someone that will let me use a windows computer to run the flash tool I guess as I cant run it on Mac OS X
Stuck on the TWRP screen, and flashing zips doesn't work, every reboot brings it to the TWRP screen and I cant seem to find system.img or boot.img in the file directory from that screen so I am thinking it ALL got wiped
Thanks for any help

Just a little FYI, you named the thread hard bricked, however you were only soft bricked. Hard Brick is a dead phone... No power, no lights, or any response.

j311slx said:
Do you mind posting what you did that was able to work? I have to wait to find someone that will let me use a windows computer to run the flash tool I guess as I cant run it on Mac OS X
Stuck on the TWRP screen, and flashing zips doesn't work, every reboot brings it to the TWRP screen and I cant seem to find system.img or boot.img in the file directory from that screen so I am thinking it ALL got wiped
Thanks for any help
Click to expand...
Click to collapse
Give this thread a try
http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508