Database Info

[Q] HELP xoom root!

ok so i rooted my xoom the other day flashed hammer head 2.1. restored my tablet to stock rooted rom buwhen i did i have now found a way to lock my device. i can boot up and have my su icon available to me however i cannot gain root access even through adb it tells me the file system is read only. so i figured i some how unrooted the device and proceeded to begin the root process for honeycomb. however when trying to push su over to the tablet it tells me the file failed to transfer because the file system is read only what do i do now? Any help would be appreciated.

Ok i have now some how erased my device completely it stops at the moto dual core boot screen. I still have cwm but thats it. Im at a loss guys. Bout to warranty this by runnin over it!
Sent from my ADR6400L using XDA Premium App

josephparlangeli said:
Ok i have now some how erased my device completely it stops at the moto dual core boot screen. I still have cwm but thats it. Im at a loss guys. Bout to warranty this by runnin over it!
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
your a noob mate seriously... these board are full of people like you... 1.. download the stock images from
http://developer.motorola.com/products/software/MZ604_HWI69.zip/
if your device is a wifi only and then push the files with fastboot...
ie.. unzip the folder into where the adb fastboot exe are
1. fastboot flash system system.img
2. fastboot flash boot boot.img
3. fastboot flash user user.img
4. fastboot flash recovery recovery.img (as you obviously cant handle root..)

Dont have to be an ass about it. But yeah already tried that when i try to push the files it tells me there is no such directory found. So i made sure in cwmr the system was mounted then it tries to transfer but tells me the directory is read only. So i tried the unlock procedure to make sure the tablet was unlocked. everything goes smoothly till i try to transfer the files again.
Sent from my ADR6400L using XDA Premium App

josephparlangeli said:
Dont have to be an ass about it. But yeah already tried that when i try to push the files it tells me there is no such directory found. So i made sure in cwmr the system was mounted then it tries to transfer but tells me the directory is read only. So i tried the unlock procedure to make sure the tablet was unlocked. everything goes smoothly till i try to transfer the files again.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Not talking mounting in cwm here bud
Get to fastboot mode not android recovery same process power plus vol down
Then flash the files not push as mounting in cwm only put the files on sd card not flashing it outright from what your reply was
I was a noob once and soft bricked everything and yet i read and read and fixed stuff myself through searching.. Cuz ultimately if its bricked what do u have to lose then ey lol just find and try everything cant make a worse paperweight than one u may already have eh
But get to fastboot not cwm then flash the files like i said and it will almost certainly work
Sent from my HTC Sensation 4G using XDA Premium App

Thats my other problem my sd card slot isnt wrkn that was my initial instinct. If i try to flash to the sd card it says no directory found. Ive used 3 different sd cards and get the same message. Im really thinkin i got a bad sd slot even when it was rooted and running i had issues with the sd card not wrking. I had several back ups on it when it did wrk and those dissappeared as well. I bought the xoom soley because of the sd card slot was pretty much going to be my saving grace when doing back ups if i ever messed up. I tried wrking it in fastboot as well if i try to flash to the system its read only. If i flash to the sd card directory not found. I know these questions are irritating to more savy individuals and i looked around trust me the last thing i like to do is say der i dun broke it i need an adult. Im just makin sure i didnt over look something more savy ppl know about. I honestly think its bricked at this point. Ive tried what you said and any other way i can think of but i alway get some kind of error.
Sent from my ADR6400L using XDA Premium App
Sent from my ADR6400L using XDA Premium App

What version of clockwork mod recovery are you using?

I believe is 4.0.0.2 i just got to wrk i know its the latest release tho.
Sent from my ADR6400L using XDA Premium App

josephparlangeli said:
I believe is 4.0.0.2 i just got to wrk i know its the latest release tho.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I would use this recovery instead of 4.0.0.2.

Ok thats a very helpful link. Did not know they had a special recovry for the xoom or realize that it wiped out all media if i didnt have this recovery. Lesson learned however i think its bricked solid now cuz it wont charge or come on at all may very well be a bad unit but i c where i went wrong with su as well i flashed 3.0 with out the chmod 4577 during the su update from cwm. Well im going to grab another one from bb and c what happens the unit is non responsive at this point. Thanks to everyone that posted here for the help.
Sent from my ADR6400L using XDA Premium App

josephparlangeli said:
Ok thats a very helpful link. Did not know they had a special recovry for the xoom or realize that it wiped out all media if i didnt have this recovery. Lesson learned however i think its bricked solid now cuz it wont charge or come on at all may very well be a bad unit but i c where i went wrong with su as well i flashed 3.0 with out the chmod 4577 during the su update from cwm. Well im going to grab another one from bb and c what happens the unit is non responsive at this point. Thanks to everyone that posted here for the help.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
you needed to flash the recovery with FASTBOOT.. not adb push chmod stuff; much easier and the process works
read the top post again.. get the recovery.img file (the v3 one the other fellow told you to grab)
1. hold the volume down button and the power button... some text will come on up the top about fasboot protocol and then
2. leave it plugged in to your computer and DONT TOUCH THE XOOM...
3. get your cmd.exe prompt window out and navigate to where your adb.exe AND fastboot.exe files are (should be tools or platform-tools...)
4. Place the recovery.img file into the explorer window where the adb.exe and fastboot.exe both are.... (this should be there as u keep trying to use adb commands but do it again to make sure)
5. type fastboot flash recovery recovery.img
thats the recovery.img flashed...

Got my xoom replaced the other day works fine have root flashed the above mention cwm and everything worked fine. Funny thing tho when they checked to see if the original device had been unlocked they said it was still locked and they gave me a replacement. Other wise id have had to use the warranty i bought. Just thought that was odd.
Sent from my ADR6400L using XDA Premium App

josephparlangeli said:
Got my xoom replaced the other day works fine have root flashed the above mention cwm and everything worked fine. Funny thing tho when they checked to see if the original device had been unlocked they said it was still locked and they gave me a replacement. Other wise id have had to use the warranty i bought. Just thought that was odd.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Well, there's your answer. You did not successfully unlock.
Glad that you learned some useful things.

flying honey comb on xoom mz601
Hi everybody. I install new image for my xoom MZ601 (tiamat last version).
Xoom from Hongkong (CHINA) with 3G.
i make all steps about unlock bootloader and root. After all that steps - i have ClockworkRecovery v 3.2.0.0 (solarnz-R4c-100611-1150). After reboot (motorola logo) i see all time honeycomb flying.
I need help.
opps: i unbrick my device on android 3.0.1. Now try again to install 3.2 by Tiamat
3.2 doesn't work. SAD

aKolp2010 said:
Hi everybody. I install new image for my xoom MZ601 (tiamat last version).
Xoom from Hongkong (CHINA) with 3G.
i make all steps about unlock bootloader and root. After all that steps - i have ClockworkRecovery v 3.2.0.0 (solarnz-R4c-100611-1150). After reboot (motorola logo) i see all time honeycomb flying.
I need help.
opps: i unbrick my device on android 3.0.1. Now try again to install 3.2 by Tiamat
3.2 doesn't work. SAD
Click to expand...
Click to collapse
You should open a new thread with your issue. Seems the OP in this one has fixed his issues by replacing his Xoom. You'll get better attention by creating a new thread in this forum.

[Q] Getting my hands on a bricked g2x today....

he said he bricked it trying to upgrade to ICS.
is the sticky at the top still the way to unbrick it? i noticed that a couple links were dead in the first post. granted i didn't go through all 17 pages, just wanted to make sure there wasn't anything newer then whats already been posted.
edit: he did say that the screen is showing s/w if that matters

Was it bricked by flashing a o2x rom? I think that may be the hardest brick I have heard of but still fixable. I believe if that is the case than following the sticky should restore the baseband and everything else.
Honestly though I would first try just reflashing CWM via nvflash, boot into recovery and load a stable GB rom. If that works, great.

LurkerRWO said:
Was it bricked by flashing a o2x rom? I think that may be the hardest brick I have heard of but still fixable. I believe if that is the case than following the sticky should restore the baseband and everything else.
Honestly though I would first try just reflashing CWM via nvflash, boot into recovery and load a stable GB rom. If that works, great.
Click to expand...
Click to collapse
he just said things went haywire when trying to flash ICS. i've been messing around with the sticky but can't get anything to work....yet!

im on windows 7 if that matters
and after i boot into recovery the screen is just flashing black. any ideas?

everything i do with flashing it just sits at the prompt saying "flashing" and nothing else happens.

blackbeasst said:
he just said things went haywire when trying to flash ICS. i've been messing around with the sticky but can't get anything to work....yet!
Click to expand...
Click to collapse
You apparently you did not even read the first post. XP only, will not work with Windows 7.
"As many have stated, pushing the v21E_00.kdz via the KDZ_FW_UPD program does work. It's just touchy.
This is a step by step guide to get you back in to working shape.
Note: You MUST do this via a PC running Windows XP. Running Vista/7 in compatibility mode is not going to work, period.
Edit: As an alternative, a virtual environment running XP will do the job. Those steps are up to you."

That's not true. I updated the baseband using win7 on my first try. No need for comparability mode.
Sent from my LG-P999 using XDA App

LurkerRWO said:
That's not true. I updated the baseband using win7 on my first try. No need for comparability mode.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Can confirm that too. Was working fine on 32 bit win7, using the method from the stickies upgrading wind's June baseband.
Sent from my LG-P999 using xda premium

duple and lurker, thanks for the confirmation that it works with 7
when i try and push the kdz i get the dreaded phone not found.

ok im on my xp machine here at work and heres what i got:
Part 1: Download the files you will need below.
V21E_00.kdz
KDZ_FW_UPD_EN
One-Click-G2x-recovery-flasher-06-16.rar
LG USB Drivers G2x
Part 2:
1) Install the LG G2x USB drivers to your WinXP machine.
2) Extract the entire contents of the One-Click recovery in to a folder and keep it handy.
3) Remove the battery from the phone. Hold both volume buttons and plug in the USB cable. If you are asked for a driver, look in the APX folder where you extracted the One-Click recovery archive.
4) Run OneClickRecoveryFlasher.exe and flash the stock recovery. Wait for the process to finish and close all windows and unplug the phone.
no problems with above steps. after that nothing works. when i put the battery back in and turn on thats when i get the flashing black screen, not back to the s/w screen.
5) Put the battery back into the phone and turn it on. You will be back at the S/W Upgrade screen. This is where you want to be! Now plug the USB cable back in to the phone. If everything is up to snuff you should have no driver problems at this point.
6) Extract KDZ_FW_UPD_EN.7z in to a folder. Inside is a msxml.msi. You need to run and install this first!
7) Run KDZ_FW_UPD.exe.. Leave the type set to CDMA and the phone mode set to DIAG. DO NOT CLICK ON "Read phone information"
8) Click the folder icon and load the V21E_00.kdz
9) Click launch software update (and pray!)

ok just for craps and giggles i tried booting into recovery and actually got the box with arrow and android! but it then reboots back to the lg screen and then flashing black screen

WOOT! finally able to get into CWM recovery!
is all that needs to be done now is install a stable rom?

double WOOT! back up and running. time to test the functionality of if though!
edit: can't find the sim and no service.

blackbeasst said:
double WOOT! back up and running. time to test the functionality of if though!
Click to expand...
Click to collapse
Delighted to hear that. So, another confirmation of the "old" folks stating it's 99.9% un-brickable.
Sent from my LG-P999 using xda premium

DupleX01 said:
Delighted to hear that. So, another confirmation of the "old" folks stating it's 99.9% un-brickable.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
and im a tard. sim was inserted bass akwards

blackbeasst said:
and im a tard. sim was inserted bass akwards
Click to expand...
Click to collapse
Congrats man.
Sent from my LG-P999

wifi seems to be flaky. keeps scanning and dropping work and home network
also it appears that the market wasn't on that version of the rom. is that a quick fix?

Now you have the recovery and baseband sorted, start from scratch and do a full wipe(including system internal/external SD). Then flash a stable ROM Weapon/EB to make sure everything is good. Just my 2 cents
Sent from my LG-P999 using xda premium

DupleX01 said:
Now you have the recovery and baseband sorted, start from scratch and do a full wipe(including system internal/external SD). Then flash a stable ROM Weapon/EB to make sure everything is good. Just my 2 cents
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
im was lucky to get it up and running, so im still a flashing noob! but what is considered a stable rom for this phone?
i grabbed one from cyanmod earlier today. i think it was from around 3/13?

blackbeasst said:
im was lucky to get it up and running, so im still a flashing noob! but what is considered a stable rom for this phone?
i grabbed one from cyanmod earlier today. i think it was from around 3/13?
Click to expand...
Click to collapse
You were lucky, indeed!
A CM nightly can be stable too, however I would flash either Weapon or Eagles Blood for a couple of days to have a piece of mind that everything is working cool. The most important would be a proper full wipe (cache, dalvik, system under mounts and storage, battery stats and imho internal and external SD too) too get rid of the previous mess caused by the unsuccessful flash, etc.
Sent from my LG-P999 using xda premium

[Q] Bricked captivate after rom flashing

Hi,
My captivate is totally bricked, HF bricked, doesn't response to any key, no light, no screen, nothing.
The sequence of events:
Former rom: myui ics - bad performance: freezing, FC
Flashed gingerbread 2.3.3 (I897UCKF1 Odin-1-Click) - worked fine.
Flashed speedmod-kernel-i897-k13e-500hz to get cm recovery full options - finished successfully but phone wouldnt go beyond samsung boot screen (before AT&T logo). I took off battery and went into recovery mode:
Installed perception rom zip file.
finished successfully,
reboot,
never woke up ever since.
Nothing helped.
I figured it's hard bricked so I tried the unbrick HW method specified here:
http://forum.xda-developers.com/showthread.php?t=1206216
I did it in professional lab exactly like the instructions.
nothing changed - the phone doesn't respond to anything.
Is there anything in the sequence I specified above which can explain what happened?
Is there any method which will unbrick the phone?

So you are saying.. turning on the power or plugging the phone in causes nothing to show up?

korockinout13 said:
So you are saying.. turning on the power or plugging the phone in causes nothing to show up?
Click to expand...
Click to collapse
Nothing.
Nada.
Sent from my GT-I9100 using XDA

There is no way that flashing a ROM zip HARD bricked your phone. That isn't possible, CWM doesn't have access to the bootloaders on any SGS device...

eitan123 said:
Nothing.
Nada.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
The unbrickablemod you linked to is the only way. Did you follow the directions on running it? http://forum.xda-developers.com/showthread.php?t=1242466
Swyped from my ICS Samsung Captivate

korockinout13 said:
The unbrickablemod you linked to is the only way. Did you follow the directions on running it? http://forum.xda-developers.com/showthread.php?t=1242466
Swyped from my ICS Samsung Captivate
Click to expand...
Click to collapse
I've tried the windows one click soft unbrick - it didnt' recognize the phone.
http://forum.xda-developers.com/showthread.php?t=1153310
I've also tried the method mentioned above throug linux and almost ended up burning my pc.
The first time in my life I got thermal trip was with this crappy ubuntu (worked for 30 minutes and almost got my proccessor on fire).
Not to mention I wasn't able to install Java.
But I did find a one click version for windows - It didnt work.
BTW, is it possible that I dont even see any charging animation?
I remember there was such animation when the phone was off.

eitan123 said:
....
BTW, is it possible that I dont even see any charging animation?
I remember there was such animation when the phone was off.
Click to expand...
Click to collapse
That means you are Hard Bricked. It will require other means than Odin or Heimdall to recover it.
Since we are not supposed to link to paid services/sites I'll just put this here:
http://lmgtfy.com/?q=Samsung+Captivate+UnBrickable+MOD+++Repair

Red_81 said:
That means you are Hard Bricked. It will require other means than Odin or Heimdall to recover it.
Since we are not supposed to link to paid services/sites I'll just put this here:
http://lmgtfy.com/?q=Samsung+Captivate+UnBrickable+MOD+++Repair
Click to expand...
Click to collapse
He's already applied that. He just needs to run the resurrector on Linux.
You cannot flash anything else. It won't work. You NEED to revive the phone first
Swyped from my ICS Samsung Captivate

Wow.... I really need more coffee today. I apologize.

korockinout13 said:
He's already applied that. He just needs to run the resurrector on Linux.
You cannot flash anything else. It won't work. You NEED to revive the phone first
Swyped from my ICS Samsung
So, is there a point running the ressurector from Linux?
What do you mean by revive it first?
I'm having hard times installing Linux and then java in it.
And I'm working in Linux environment.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse

eitan123 said:
korockinout13 said:
He's already applied that. He just needs to run the resurrector on Linux.
You cannot flash anything else. It won't work. You NEED to revive the phone first
Swyped from my ICS Samsung
So, is there a point running the ressurector from Linux?
What do you mean by revive it first?
I'm having hard times installing Linux and then java in it.
And I'm working in Linux environment.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Based on the directions, it seems that you need Linux. I find it really easy to use the Ubuntu windows installer. It doesn't mess with partitions and is easy to uninstall. What are you having problems with?
All I'm trying to say about reviving is the fact that Odin or Heimdall will do nothing until you run the unbrickablemod program
Swyped from my ICS Samsung Captivate
Click to expand...
Click to collapse

Maybe I'm missing something.
I booted from Linux CD and ran resscuration.
It didn't recognize the phone.
An I doing it correctly?
Btw, out was easy installing Ubuntu.
The problem was I got CPU thermal trip and forced shut down.
Sent from my GT-I9100 using XDA

[How to] Root and Flash custom roms

This thread is just to direct all the noobs into the right direction, related to root and flash new roms in the Inspire 4G.
[*]Rooting and reverting to stock
Due to the retirement of the Hack Kit, rooting methods have been reduced to:
http://forum.xda-developers.com/showthread.php?t=2168500
or if you are skilled in using adb and fastboot commands:
http://tau.shadowchild.nl/attn1/?cat=6
If you are still stuck and want to revert your phone back to out of the box, then use Marsdta's Guide:
http://forum.xda-developers.com/showthread.php?t=1396229
or Gene Poole's Tool (that will revert also S-OFF):
http://forum.xda-developers.com/showthread.php?t=1208507
[*]Flashing a Custom Rom
To flash a custom rom you need to be rooted and S-OFF (if u used the Hack Kit) or have and unlocked bootloader using HTCDEV tool (wich I don't suggest)
Once u are S-OFF and have CWM or some other custom recovery installed (I personally prefer 4ext) you have to follow these steps (read the dev's thread about particularities. This is just a general guide on how to do it):
Download the custom rom .zip file and put it in your sdcard. Make sure that u check md5sum first just to avoid bootloops.
Reboot phone in recovery. There are many ways to do that, the first can be using Rom Manager (I don't suggest using it for anything else but that) and choosing reboot in recovery option. The second way is to boot in bootloader (press power down and reboot choosing hboot) or just turn phone off and power it up pressing power and volume down. And the last is to use adb commands. Plug the phone as charge only with usb debugging on, open a cmd as admin or terminal as root in your PC and then type adb reboot recovery.
Once in recovery, you need to do a full wipe (wipe data / factory reset and wipe cache + dalvik cache). You can also format some other partitions such as data and system, but the full wipe will work.
When full wipe is finished, go to flash zip from sdcard option, choose zip file and then flash that file.
Reboot the phone once it has finished flashing and wait for the device to fully reboot. The first boot will take a while (probably longer than usual) so don't get scared.
If you flashed a CM based rom, you need to flash google apps separately as well, so find the gapps file corresponding to your rom and flash it in the same manner as above described.
Trouble Shooting
Bootloops: If your phone repeats over and over the bootanimation, don't panic, you are not bricked. Something must have gotten wrong but you can reboot in recovery and re flash the rom as previously described. If bootloop is still there, then try downloading the zip again or choose a diffrent rom.
Factory Reset: If you factory reset the phone and you are not stock, then the phone won't have a rom...you will get stuck in the splash screen (white screen with the green HTC). Just do as described above, get a rom to the sdcard and then flash it. You are not bricked, you are just stuck
Well, this was just to try to point you in the right direction. If you think that I missed something, feel free to tell me and will add it to the OP.....Salud! :good:

Reserved just in case
Well done glevitan. On a side note, I finally understood how to use adb. Thanks.
Sent from a dream.

Teichopsia said:
Reserved just in case
Well done glevitan. On a side note, I finally understood how to use adb. Thanks.
Sent from a dream.
Click to expand...
Click to collapse
Thanks, let's hope that people find it usefull...

To help your thread going however 'slightly' off topic it may be, but since you did mention adb, I finally managed to get apk multi tool and sdk manager installed, and with a slight hiccup getting the adb to recognize my device (I started all of this last night), I believe I have everything I need?
Now I need to learn what I can do with those.
All of this would have taken me half the time if I were 15 again
Sent from a dream.

Teichopsia said:
To help your thread going however 'slightly' off topic it may be, but since you did mention adb, I finally managed to get apk multi tool and sdk manager installed, and with a slight hiccup getting the adb to recognize my device (I started all of this last night), I believe I have everything I need?
Now I need to learn what I can do with those.
All of this would have taken me half the time if I were 15 again
Sent from a dream.
Click to expand...
Click to collapse
hahaha...ummmm you shouldn't have problems. Just install SDK and apk multi tool in the SDK>tools folder or somewhere else. Then from command prompt you should be able to run the commands for the apk multi tool. I use the apktool and I have no problem at all. The main thing is to have adb installed...but there's no need to have the phone plugged to use the apk tool.
In the case of your device, make sure that u have the HTC drivers installed, if you have HTC Sync, you should have them...to try that just plug the phone as charge only, make sure that usb debugging is on and then open a cmd as admin and type adb devices...you should see your HTCserialnumber....

I didn't know I didn't need to have the cell plugged in, nice to know.
I had done all of that and it was working.... IT WAS WORKING , I decided to move a few folders around, something got messed up, tried placing them where they were, still no go, it's not recognizing my device anymore.
Don't worry, I'll figure it out eventually, but the problem is my head is going to start hurting any minute now. I'll be back shortly to ask you something you mentioned and I've read which I simply don't get - well, maybe not as shortly as I would like.
Edit: whenever I run the adb devices command it has to be done withing the folder where the adb.exe is located, right?
2nd edit: found it and it's working.
To run the adb devices command, which means going to that specific folder, would be seperate from using the apk tool? Would have moving the folders around somehow messed up the way apk tool would work? Im not even sure if im asking the right question
3rd edit: when you said to install the apk tool and sdk in the same folder, well, I already installed both of them to the default location.... what do you mean by that? Should I move them if they are not there? And if I may ask why?
Sent from a dream.

Teichopsia said:
I didn't know I didn't need to have the cell plugged in, nice to know.
I had done all of that and it was working.... IT WAS WORKING , I decided to move a few folders around, something got messed up, tried placing them where they were, still no go, it's not recognizing my device anymore.
Don't worry, I'll figure it out eventually, but the problem is my head is going to start hurting any minute now. I'll be back shortly to ask you something you mentioned and I've read which I simply don't get - well, maybe not as shortly as I would like.
Edit: whenever I run the adb devices command it has to be done withing the folder where the adb.exe is located, right?
2nd edit: found it and it's working.
To run the adb devices command, which means going to that specific folder, would be seperate from using the apk tool? Would have moving the folders around somehow messed up the way apk tool would work? Im not even sure if im asking the right question
3rd edit: when you said to install the apk tool and sdk in the same folder, well, I already installed both of them to the default location.... what do you mean by that? Should I move them if they are not there? And if I may ask why?
Sent from a dream.
Click to expand...
Click to collapse
What I did, that doesn't mean that is the correct way.... I installed SDK and in the tools folder I installed the apktool. You don't need to be in that folder to run the adb command...I don't do it that way...I just run the command from where I am...

glevitan said:
What I did, that doesn't mean that is the correct way.... I installed SDK and in the tools folder I installed the apktool. You don't need to be in that folder to run the adb command...I don't do it that way...I just run the command from where I am...
Click to expand...
Click to collapse
Right now I feel I'm way over my head. And that includes my choice of using eclipse. I'm not even sure what I can do with all these tools...
My hat off to you guys.
Sent from a dream.

Teichopsia said:
Right now I feel I'm way over my head. And that includes my choice of using eclipse. I'm not even sure what I can do with all these tools...
My hat off to you guys.
Sent from a dream.
Click to expand...
Click to collapse
I don't know either....but it is worth trying....see Adam's tutorials...are awesome. Maybe some day I will learn what to do with all this as well!! lol

glevitan said:
I don't know either....but it is worth trying....see Adam's tutorials...are awesome. Maybe some day I will learn what to do with all this as well!! lol
Click to expand...
Click to collapse
Back and forth
I don't believe that was the link you gave me on the other side. Perhaps posting over here will refresh your memory...?
Sent from a dream.

Teichopsia said:
Back and forth
I don't believe that was the link you gave me on the other side. Perhaps posting over here will refresh your memory...?
Sent from a dream.
Click to expand...
Click to collapse
AHH I was talking about Adamsoutler´s tutorial in XDA TV. He explains how to set SDK and develop APKs....it is awesome!..look at the XDA TV thread.

Bump.
Sent from a dream.

not able to go back to stock
I unlocked my htc inspire and tried to root it. Now i ended up with a ccwm recovery and S on unlocked bootloader .
I tried to go back to stock rom and have tried this guide and other guides also but was unsuccessful . My phone is running gizroot v2 but with taht the wifi mac address is unavailable . So i canniot access wifi .
If i put PD98IMG .zip in the root directory then it does not prompt me to any installation in the bootloader .
Please help

krjkinan said:
I unlocked my htc inspire and tried to root it. Now i ended up with a ccwm recovery and S on unlocked bootloader .
I tried to go back to stock rom and have tried this guide and other guides also but was unsuccessful . My phone is running gizroot v2 but with taht the wifi mac address is unavailable . So i canniot access wifi .
If i put PD98IMG .zip in the root directory then it does not prompt me to any installation in the bootloader .
Please help
Click to expand...
Click to collapse
RUUs can not be flashed with an unlocked bootloader. Relock it first, then run the RUU.

Can some one help me. I want to riot my htc inspire 4g
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

romanvaldezo said:
Can some one help me. I want to riot my htc inspire 4g
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This post is no longer timely. The tool it refers to has been retired. You can no longer get S-Off, but you can unlock the bootloader: http://forum.xda-developers.com/showthread.php?t=2169515.

hey
hey not being mean but you guys dont actually help ive been on this site looking for a tutorial for weeks and cant find one i need to root my htc inspire plzz help

rty123456 said:
hey not being mean but you guys dont actually help ive been on this site looking for a tutorial for weeks and cant find one i need to root my htc inspire plzz help
Click to expand...
Click to collapse
Hey, not being mean, but did you read the post right above yours...? Or anything in the Desire HD forums, which is the same phone and is more populated?

rty123456 said:
hey not being mean but you guys dont actually help ive been on this site looking for a tutorial for weeks and cant find one i need to root my htc inspire plzz help
Click to expand...
Click to collapse
Then are not reading the OP. You have all the information neeeded in there...if your first post in here Is to whine, then you have not Read the rules or understand the spirit of xda.
Follow the instructions And You will be fine, if You don't Get them take time To learn. Nobody Is going To do your homework.

I just recently rooted my inspire it took some time reading and a few attempts to get it down. But after my homework and grasping the concept it was fairly easy.
Sent from my Desire HD using xda app-developers app

[Q] Bricked??

i recently tried to install jellybean but the rom did not work on nexus s, i stupidly removed the only working rom from my 'sd' card and now my phone only boots into a black screen, i have tried to put a known working rom on my phone but every pc i try to connect my phone to says the device has malfunctioned and windows cannot install software. i have tried to use adb but that also cannot find my device. am i looking at getting another nexus with a broken screen and using my working screen to gain a decent phone back or am i missing a vital programme that will fix my utter cockup? thanks in advance

Are you familiar with adb? Because unless you have the right drivers, you phone won't be recognized. Also, usually your computer won't notify you when you're connected and able to use adb, you have to start the interaction through cmd.exe. this being said, try adb again to move a rom or backup into your device.
Also, can you boot into fastboot? If so, is there a warning message or anything?
Sent from my Nexus S using xda app-developers app

FirePoncho86 said:
Are you familiar with adb? Because unless you have the right drivers, you phone won't be recognized. Also, usually your computer won't notify you when you're connected and able to use adb, you have to start the interaction through cmd.exe. this being said, try adb again to move a rom or backup into your device.
Also, can you boot into fastboot? If so, is there a warning message or anything?
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
i am only famililar with adb to the point of rooting, i have tried to download the drivers but only can see .dll files in the driver folders no option to install said drivers. i can get into power and vol up if that is fastboot?? the problem been is i installed a rom which was meant for the nexus s and i didnt read all comments and later found out it does not work with the nexus. i now cannot access the sd storage to put a working rom onto it . when i open cmd and type adb shell it says device not found. brains ready to explode right now. any help on adb is greatly appriciated

Fast boot is when you phone is off, you turn it on by pressing volume up+power at the same time. Let me know if there is a warning text in red at the top.
Do you know how to flash factory images? Because you may be able to do that to get a stock os on your phone. It would wipe everything, however. Flashing a factory image doesn't require you to open SD storage. I'd link you to the thread with the tutorial, but I'm on mobile :/ ill post it if i get a chance, i know its floating around in the nexus s android forums
Sent from my Nexus S using xda app-developers app

FirePoncho86 said:
Fast boot is when you phone is off, you turn it on by pressing volume up+power at the same time. Let me know if there is a warning text in red at the top.
Do you know how to flash factory images? Because you may be able to do that to get a stock os on your phone. It would wipe everything, however. Flashing a factory image doesn't require you to open SD storage. I'd link you to the thread with the tutorial, but I'm on mobile :/ ill post it if i get a chance, i know its floating around in the nexus s android forums
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
i do not know how to flash factory images, im am very much a noob to rooted phones and playing with software.
i can get into fastboot and at the bottom it says
usb control init
usb control init end
top says fastboot mode
product name herring
hw version rev 11
bootloader version i9020xxka3
baseband version i9020xxkd1
carier info eur
ser 33304eb5103500ec
lock state unlocked
my laptop does not recognise the phone so i dont know how to flash a factory image. this is the cmd sequence i get
adb shell
error device not found
tried mounting sd card and data but no joy
also tried mounting usb storage.
all i get is device has malfunctioned and will not run
tried downloading google usb drivers and samsung drivers all to no avail.
fingers crossed you can tell me something i dont know as i really cant afford to buy a new phone

Well it seems you sdcard isn't dead, which is good! When mine was, fastboot gave me an error.
Now IMO, you should be able to flash a stock recovery image. This will clear everything you have on ur phone, but it should get it back to working condition.
Ill post a tutorial on how to do it tomorrow, that's the soonest i can get on a computer. It is not that hard, and it helps when you're already somewhat familiar with adb. I used to be a noob too, now I'm slightly less noobish!
So as i said, i think i have a solution, ill post how tomorrow, when i have a PC (in on mobile right now).
Cheers, i hope i can fix your phone!
Sent from my Nexus S using xda app-developers app

FirePoncho86 said:
Well it seems you sdcard isn't dead, which is good! When mine was, fastboot gave me an error.
Now IMO, you should be able to flash a stock recovery image. This will clear everything you have on ur phone, but it should get it back to working condition.
Ill post a tutorial on how to do it tomorrow, that's the soonest i can get on a computer. It is not that hard, and it helps when you're already somewhat familiar with adb. I used to be a noob too, now I'm slightly less noobish!
So as i said, i think i have a solution, ill post how tomorrow, when i have a PC (in on mobile right now).
Cheers, i hope i can fix your phone!
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
much appriciated and i hope you can too. thank you thank you thanks you

Alright, so this is the guide to install a factory image: http://forum.xda-developers.com/showthread.php?t=1572307
What a factory image will do, is restore your phone completely to a new like state. That being said, you will lose anything you have on the phone (picture, music, etc..). I don't know of any other way to help, so if you're willing to lose everything, but get your phone working, continue reading.
-First, you have to determine what model on Nexus S you have. If you're on AT&T or Rogers, you have an I9020A, and you have to download the "sojua" factory image. If you're on T-mobile, or have the version with an S-LCD display (as opposed to the normal AMOLED), you have to flash the "soju" factory image. If you're not sure what version you have, let me know what carrier you're with.
-Second, download the Factory image corresponding to your phone from the link I posted, as for version, that's up to you, but I recommend 4.1.2 (JB).
-Third, Make sure you have all the right drivers, and the android-sdk installed. You should already have this, since you've use adb before.
-Fourth, follow steps 1,2,3 and 4A in the link I posted above.
Follow these instruction, and if you do not understand them before doing the procedure, just ask a question here! good luck!

FirePoncho86 said:
Alright, so this is the guide to install a factory image: http://forum.xda-developers.com/showthread.php?t=1572307
What a factory image will do, is restore your phone completely to a new like state. That being said, you will lose anything you have on the phone (picture, music, etc..). I don't know of any other way to help, so if you're willing to lose everything, but get your phone working, continue reading.
-First, you have to determine what model on Nexus S you have. If you're on AT&T or Rogers, you have an I9020A, and you have to download the "sojua" factory image. If you're on T-mobile, or have the version with an S-LCD display (as opposed to the normal AMOLED), you have to flash the "soju" factory image. If you're not sure what version you have, let me know what carrier you're with.
-Second, download the Factory image corresponding to your phone from the link I posted, as for version, that's up to you, but I recommend 4.1.2 (JB).
-Third, Make sure you have all the right drivers, and the android-sdk installed. You should already have this, since you've use adb before.
-Fourth, follow steps 1,2,3 and 4A in the link I posted above.
Follow these instruction, and if you do not understand them before doing the procedure, just ask a question here! good luck!
Click to expand...
Click to collapse
still adb cannot find device.......... any links for known drivers for nexus s on win 7 64 bit?

You might need to reinstall the android SDK and drivers, there should be a link in the link i sent you to show how to do that.. If adb still doesn't recognise, your main board might be fried
Sent from my Nexus S using xda app-developers app

FirePoncho86 said:
You might need to reinstall the android SDK and drivers, there should be a link in the link i sent you to show how to do that.. If adb still doesn't recognise, your main board might be fried
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
reinsalled sdk tools, still phone not recognised by laptop. gonna try get a cheaper android and flog this one on ebay as someone else might know how to repair it. thank you for your time and help but it appears its all in vain......... damn stupid phone!

[deleted]

Rodya234 said:
the phone is probably fine if you can get into fast boot.
Click to expand...
Click to collapse
What I'm saying! You can get it to boot, but just not into anything..
Sent from my Nexus S using xda app-developers app

FirePoncho86 said:
What I'm saying! You can get it to boot, but just not into anything..
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
i wish someone could just see this, pdanet asks me to connect my phone to finnish installing the drivers, problem is the phone is NOT RECOGNISED i know exactly what you are all saying to do but my phone will not connect at all. more than happy to post it to one of you guys on here to fix but like i said ive tried everything and have pulled nearly all my hair out in the process

Samsung repair? I know what you're talking about, it happened to me, I was completely bricked, all I could so was send it to Samsung repair..
Sent from my Nexus S using xda app-developers app

Damn, if only you could get it recognized you'd probably be able to flash custom recovery through fastboot and I guess you'd be able to install from sd without data loss.
Sent from my Nexus S