i posted this here cause no one answers my Q&A posts, but here's the story - i was running CM7 on my phone and i was having problems with my phone and decided to restore to stock and unroot via PD15IMG.zip, but i didnt know how to undo gfree cause grankin's instructions are all over the place. so the PD15IMG.zip did it's thing but it says update failed and reboot. so i reboot and the phone goes to the android recovery, not the CWM recovery. what do i do to get back on track, cause its not bricked if i can go to the bootloader and recovery, right? im stuck
This may or may not be the issue, but what recovery version are you running?
TeeJay3800 said:
This may or may not be the issue, but what recovery version are you running?
Click to expand...
Click to collapse
well, it WAS CWM 3.0.0.6 but now it's the stock android recovery, i think i might try installin CWM by adb since s is still off...
I2IEAILiiTY said:
well, it WAS CWM 3.0.0.6 but now it's the stock android recovery, i think i might try installin CWM by adb since s is still off...
Click to expand...
Click to collapse
You can use ADB or even fastboot if you have the engineering SPL. Once you have a good recovery installed, it's just a matter of wiping everything and flashing a stable ROM. If CM7 didn't work well for you but you want Gingerbread and the plain Android look, try RoyalGinger.
TeeJay3800 said:
You can use ADB or even fastboot if you have the engineering SPL. Once you have a good recovery installed, it's just a matter of wiping everything and flashing a stable ROM. If CM7 didn't work well for you but you want Gingerbread and the plain Android look, try RoyalGinger.
Click to expand...
Click to collapse
i decided to reroot cause all roms i installed, even after clean wipes, would lag and be unresponsive at times. and what's SPL? i'm kinda new to the android game, but iphones and ipods are a different story...
I2IEAILiiTY said:
i decided to reroot cause all roms i installed, even after clean wipes, would lag and be unresponsive at times. and what's SPL? i'm kinda new to the android game, but iphones and ipods are a different story...
Click to expand...
Click to collapse
The SPL is often referred to as "hboot" or "bootloader". It sounds like you're having enough trouble as it is, so I wouldn't worry about that. If you still have S-OFF, then you're still rooted. I honestly don't think that un-rooting and the re-rooting will solve your problems. It's possible your previous recovery was corrupt, that's why everything you flashed was slow (although apps and setups can also cause that). I would flash CWM 3.0.0.6 via ADB and then try another ROM.
TeeJay3800 said:
The SPL is often referred to as "hboot" or "bootloader". It sounds like you're having enough trouble as it is, so I wouldn't worry about that. If you still have S-OFF, then you're still rooted. I honestly don't think that un-rooting and the re-rooting will solve your problems. It's possible your previous recovery was corrupt, that's why everything you flashed was slow (although apps and setups can also cause that). I would flash CWM 3.0.0.6 via ADB and then try another ROM.
Click to expand...
Click to collapse
Or too much of a load for the CPU settings if he has it Under or over clocked... or a bad kernel (aka not one fauxs ;D )
Sent from my HTC Glacier using XDA Premium App
TeeJay3800 said:
The SPL is often referred to as "hboot" or "bootloader". It sounds like you're having enough trouble as it is, so I wouldn't worry about that. If you still have S-OFF, then you're still rooted. I honestly don't think that un-rooting and the re-rooting will solve your problems. It's possible your previous recovery was corrupt, that's why everything you flashed was slow (although apps and setups can also cause that). I would flash CWM 3.0.0.6 via ADB and then try another ROM.
Click to expand...
Click to collapse
how do i get adb to work in bootloader? cause it obviously wont in the android recovery
Nicgraner said:
Or too much of a load for the CPU settings if he has it Under or over clocked... or a bad kernel (aka not one fauxs ;D )
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
i've used faux's and grankin's...it's still bad
I2IEAILiiTY said:
how do i get adb to work in bootloader? cause it obviously wont in the android recovery
Click to expand...
Click to collapse
just kidding, i figured it out...
but when i try to use the method on unlockr.com (not sure if everyone does it this way) i cant navigate to adb via the command terminal
See here for instructions on setting up ADB. You can't use ADB while in your bootloader, that's what fastboot is for. ADB is done with the phone fully booted.
I2IEAILiiTY said:
just kidding, i figured it out...
but when i try to use the method on unlockr.com (not sure if everyone does it this way) i cant navigate to adb via the command terminal
Click to expand...
Click to collapse
alright, the problem right now is, i've figured out how to use usb on my f***ed up phone, but the drivers won't install, and adb is still being a pain in the arse.
I2IEAILiiTY said:
alright, the problem right now is, i've figured out how to use usb on my f***ed up phone, but the drivers won't install, and adb is still being a pain in the arse.
Click to expand...
Click to collapse
That doesn't tell me much. Do you get an error when running "htcdrivers.exe" during the setup procedure?
TeeJay3800 said:
That doesn't tell me much. Do you get an error when running "htcdrivers.exe" during the setup procedure?
Click to expand...
Click to collapse
lol, just kidding. i didn't see your post til i said that. alright, so do i type fastboot devices or whatever from the command menu and then install CWM?
I2IEAILiiTY said:
lol, just kidding. i didn't see your post til i said that. alright, so do i type fastboot devices or whatever from the command menu and then install CWM?
Click to expand...
Click to collapse
It is that simple, but only if you have the engineering SPL/hboot/bootloader. Towards the bottom of this post is instructions for flashing that.
TeeJay3800 said:
It is that simple, but only if you have the engineering SPL/hboot/bootloader. Towards the bottom of this post is instructions for flashing that.
Click to expand...
Click to collapse
yea...i didn't take the risk of flashing that when i rooted my phone...will i still be able to flash this recovery img?
I2IEAILiiTY said:
yea...i didn't take the risk of flashing that when i rooted my phone...will i still be able to flash this recovery img?
Click to expand...
Click to collapse
Yes, in fact fastboot is the safest way to flash things like recoveries. Once the SPL is installed, boot the phone normally, connect ADB, enter "reboot bootloader", once the phone has booted into the SPL enter "fastboot flash recovery recovery.img" and press enter. Just remember to have the IMG file in the ADB folder of your computer.
TeeJay3800 said:
Yes, in fact fastboot is the safest way to flash things like recoveries. Once the SPL is installed, boot the phone normally, connect ADB, enter "reboot bootloader", once the phone has booted into the SPL enter "fastboot flash recovery recovery.img" and press enter. Just remember to have the IMG file in the ADB folder of your computer.
Click to expand...
Click to collapse
so, in order to complete this, do i need the engineering hboot?
Only to do it via fastboot (the safest way). You can also do it from the terminal emulator while the phone is booted normally.
TeeJay3800 said:
Only to do it via fastboot (the safest way). You can also do it from the terminal emulator while the phone is booted normally.
Click to expand...
Click to collapse
my phone is still stuck in the boots and recoveries is the problem. i don't have the engineering hboot and when i try to flash the recovery.img it says writing recovery...failed
Related
Please help me. I just got it yesterday. My girlfriend was already complaining about me spending the money on it. Now when she gets home...oh boy. I was trying to change the color of the status bar. I went into system/framework, restarted and now it's stuck at the T-Mobile screen.
I just rooted it with adb. I don't have the Clock recovery installed. I don't have alot of time either. Please tell me my options. Here is my hboot screen.
VISION PVT SHIP S-OFF
H-BOOT-0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Sep 2 2010, 17:59:38
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
MobileWon said:
Please help me. I just got it yesterday. My girlfriend was already complaining about me spending the money on it. Now when she gets home...oh boy. I was trying to change the color of the status bar. I went into system/framework, restarted and now it's stuck at the T-Mobile screen.
I just rooted it with adb. I don't have the Clock recovery installed. I don't have alot of time either. Please tell me my options. Here is my hboot screen.
VISION PVT SHIP S-OFF
H-BOOT-0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Sep 2 2010, 17:59:38
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Click to expand...
Click to collapse
Every phone i have had from the g1, mytouch 3g, vibrant, and now g2 it never fails to amaze me how people who dont know what they are doing manage to brick their phone in under a day. PROTIP READ learn what you are doing before you go in doing it so you dont screw yourself.
If you have the hboot menu and you seem to have s-off so you can restore official htc rom or a custom rom
Sent from my HTC Vision using XDA App
Yeah. Best bet would be to flash a custom recovery through fastboot and then reinstall the stock rooted rom or install a custom ROM.
And hopefully not make things worse botching the recovery flash
Hot_Hands said:
Yeah. Best bet would be to flash a custom recovery through fastboot and then reinstall the stock rooted rom or install a custom ROM.
And hopefully not make things worse botching the recovery flash
Click to expand...
Click to collapse
Yup, exacly what he said.. also, I don't think editing the statusbar from a stock is possible because its odexed, correct me if I am wrong though.. unless you really know what you're doing.. so now after flashing recovery, try again with a nandroid if you have yours if not with fastludeh's stock odex or deodex rom if you want to keep it stock.
Sent from my HTC Vision
You'll need to download this to your android-sdk tools folder:
http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.1.2-vision.img
Then go into fastboot and type
fastboot erase recovery
followed by
fastboot flash recovery recovery-clockwork-2.5.1.2-vision.img
From there you should put a custom ROM (probably CM6 or enomthers) or rooted stock as advised above on your SD card, boot into clockwork, wipe system/data and install the ROM (and gapps if you do CM6).
And please remember: nandroids are your friend
Hot_Hands said:
You'll need to download this to your android-sdk tools folder:
http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.1.2-vision.img
Then go into fastboot and type
fastboot erase recovery
followed by
fastboot flash recovery recovery-clockwork-2.5.1.2-vision.img
From there you should put a custom ROM (probably CM6 or enomthers) or rooted stock as advised above on your SD card, boot into clockwork, wipe system/data and install the ROM (and gapps if you do CM6).
And please remember: nandroids are your friend
Click to expand...
Click to collapse
Thanks, I,m gonna go with the enomthers rom. Do I need to rename it before flashing?
MobileWon said:
Thanks, I,m gonna go with the enomthers rom. Do I need to rename it before flashing?
Click to expand...
Click to collapse
Nope. Just put it on your SD and flash from recovery.
MobileWon said:
Thanks, I,m gonna go with the enomthers rom. Do I need to rename it before flashing?
Click to expand...
Click to collapse
No, you do not need to rename it.
Sent from my HTC Vision using XDA App
MobileWon said:
Thanks, I,m gonna go with the enomthers rom. Do I need to rename it before flashing?
Click to expand...
Click to collapse
And just so you know, your lucky that you flashed the ENG HBOOT, without that, you would have been screwed.
EDIT: Oh wait, it says SHIP S-OFF, shouldn't it say ENG S-OFF if you had the ENG boot loader? Did you even flash the new HBOOT?
KoolKidsKlub said:
And just so you know, your lucky that you flashed the ENG HBOOT, without that, you would have been screwed.
Click to expand...
Click to collapse
Wait, does he have engineering HBOOT installed? The HBOOT screen he listed says SHIP. Without the ENG HBOOT, he won't be able to fastboot the ClockworkMod Recovery.
To the OP, you probably will have to flash back to the official HTC ROM. See this thread: http://forum.xda-developers.com/showthread.php?t=788489.
And yes, as others have stated, you should make a nandroid backup prior to messing with system files. You cannot edit the framework without DEODEX-ing the system first.
ianmcquinn said:
Wait, does he have engineering HBOOT installed? The HBOOT screen he listed says SHIP. Without the ENG HBOOT, he won't be able to fastboot the ClockworkMod Recovery.
To the OP, you probably will have to flash back to the official HTC ROM. See this thread: http://forum.xda-developers.com/showthread.php?t=788489.
And yes, as others have stated, you should make a nandroid backup prior to messing with system files. You cannot edit the framework without DEODEX-ing the system first.
Click to expand...
Click to collapse
Yeah I just noticed that and edited my post about 1-2 minutes ago.
Ok, I entering these commands in cmd window right? Just like I did for rooting, right? If so, it said failed, not allowed when I input fastboot erase recovery.
The guys above were right. I saw s-off and assumed you had the eng-hboot. Sorry. At this point you're going to have to flash an RUU and go back to stock and then try again.
MobileWon said:
Ok, I entering these commands in cmd window right? Just like I did for rooting, right? If so, it said failed, not allowed when I input fastboot erase recovery.
Click to expand...
Click to collapse
Yeah ummm you might be screwed, we assumed that you flashed the engineering HBOOT, and only with the engineering HBOOT can you use fastboot to save your self and it seems like you don't have it. I'm not sure what to do now, I think some one said that you might have to flash the stock ROM but I'm not sure how. Wait around for some other guys to help you out, they know more than me with this stuff.
Hot_Hands said:
The guys above were right. I saw s-off and assumed you had the eng-hboot. Sorry. At this point you're going to have to flash an RUU and go back to stock and then try again.
Click to expand...
Click to collapse
Ok, I have the stock rom already. How do I flash a RUU? Or can you give me a link?
Hot_Hands said:
The guys above were right. I saw s-off and assumed you had the eng-hboot. Sorry. At this point you're going to have to flash an RUU and go back to stock and then try again.
Click to expand...
Click to collapse
Are you sure he can do that? Because theres like a sticky in the dev section of the forums saying NOT to do that unless you know what your doing or only if you flash the EXACT same ROM that came shipped with your phone, or something like that.
EDIT: And if you do have to flash an RUU, could you please explain how? I would like to know how just in case I screw something up(which I probably won't because I have been on my computer searching the forum, asking for help and to double check that what I have learned is correct and what to do if something bad happens for the past week or two) and I can also use the information to help other users.
KoolKidsKlub said:
Are you sure he can do that? Because theres like a sticky in the dev section of the forums saying NOT to do that unless you know what your doing or only if you flash the EXACT same ROM that came shipped with your phone, or something like that.
Click to expand...
Click to collapse
That was a warning because if you had S-Off and root it would put S-On and remove root. It was an issue because for a while it was impossible to root the DZ's 1.72 RUU but this has since been worked around and doesn't apply to the G2.
Ok, guys Im not an idiot. I previously had a HD2 and had no problems...just rushing to get my phone right before I go out of town for the weekend. So, whatever I have to do to get it right.
KoolKidsKlub said:
Are you sure he can do that? Because theres like a sticky in the dev section of the forums saying NOT to do that unless you know what your doing or only if you flash the EXACT same ROM that came shipped with your phone, or something like that.
Click to expand...
Click to collapse
You might be right.
Ok,... So you have gone into your Hboot screen, select fastboot, then it says Fastboot on the screen yeah? Do:
fastboot devices
in cmd, do you get anything?
So, he's running a custom ROM right now, the latest desire hd port, GB, etc.
Well, most everything else needs CWM 3.006 or whatever. So, I'm trying to flash that. BUT, his phone acts as if he doesn't have root. I't S-offed and has "su" (the app) but it just doesn't work.
Tried flashing cwm with fastboot, "permission denied"
Idk what else to do
Regards
Smith
smithisize said:
So, he's running a custom ROM right now, the latest desire hd port, GB, etc.
Well, most everything else needs CWM 3.006 or whatever. So, I'm trying to flash that. BUT, his phone acts as if he doesn't have root. I't S-offed and has "su" (the app) but it just doesn't work.
Tried flashing cwm with fastboot, "permission denied"
Idk what else to do
Regards
Smith
Click to expand...
Click to collapse
doubt its bricked...(its not bricked if you can get to the bootloader
what h-boot version do you have?
use the PD15IMG.zip to restore your phone
VibrantOwnr said:
what h-boot version do you have?
Click to expand...
Click to collapse
86.0.0.0 i believe... I followed the perm root tut before flashing this custom ROM, then he messed it up..
smithisize said:
86.0.0.0 i believe... I followed the perm root tut before flashing this custom ROM, then he messed it up..
Click to expand...
Click to collapse
i dont think you can flash using fastboot in .86.
if it wont boot to the rom try the PD15IMG.zip file to restore
if it boots to the rom, go back to the true s-off/permroot guide in the development section and flash your bootloader (there is directions at the bottom of the first post (the post with the instructions))
After that it should work for fastboot
You can alternatively flash recovery through rom manager (off of the market..the free version will do)
VibrantOwnr said:
i dont think you can flash using fastboot in .86.
if it wont boot to the rom try the PD15IMG.zip file to restore
if it boots to the rom, go back to the true s-off/permroot guide in the development section and flash your bootloader (there is directions at the bottom of the first post (the post with the instructions))
After that it should work for fastboot
You can alternatively flash recovery through rom manager (off of the market..the free version will do)
Click to expand...
Click to collapse
ROM Manager didn't work (again, couldn't obtain permissions).
So, I'm going to flash the ROM, hope for the best, then if $*&^ hits the fan, I'll result to flashing a diff bootloader.
Thanks for your advice, didn't think about flashing a diff booloader... used to my Cappy xD
Regards
Smith
have you tried using TrueBlue's recovery .zip it was the only way I could get either of my phones to take 3.0.0.6
HERE is the thread for it
Well, I flashed regardless of the 3006 req, and it went fine... Whatever lol.
thanks for the help and suggestions
Regards
Smith
Rooted with the "check this out even if" thread. Worked fine, found out that gfree doesn't root, but that visionary is what actually roots you when using it for teh second time after gfree turns radio security off. (had su denied in terminal a few times after gfree until I ran visionary and rebooted twice- it finally took)
So a big thanks to everyone.
The question is- at the end of the above thread, it says 0.85 bootloader is not necessary to flash a rom (i'm on royal ginger now so i know that), but that it would help avoid bricks in the future. Meanwhile, on the CM wiki for MT4G, it goes thru the abd rooting method, and it says that bootloader is not recommended.
Now, which is it? I don't want one of these
http://forum.xda-developers.com/showthread.php?t=1028615
where I read that there's people who flash one rom a single time like royalginger 1.6, then want to goto CM7.02 or vice versa, and that's all it takes to get in some boot loop. Now it might be that they're not wiping everything they should wipe, or wipe once instead of twice (which shouldnt be necessary), but it still makes you wonder.
Should I flash the 085 bootloader? Running fine on RG1.6, but may try CM 7.02 or RG2.0 when it's out of testing...
Thanks
acsi007 said:
The question is- at the end of the above thread, it says 0.85 bootloader is not necessary to flash a rom (i'm on royal ginger now so i know that), but that it would help avoid bricks in the future. Meanwhile, on the CM wiki for MT4G, it goes thru the abd rooting method, and it says that bootloader is not recommended
Click to expand...
Click to collapse
The engineering bootloader is not required, but some of us do recommend it. IF you should have something go south you can flash recovery images, sections of the ROM, erase sections of the ROM, clear stuff. It helps if you should run into a problem. Their have been a few threads that people would of bricked their devices if they didn't have it.
The final choice is up to you. But if it were my phone i'd do it. If you are worried about the code you have to punch in to unlock it, just double and triple check it.
hmm... what is it specifically that i cant do if i don't flash the engineering bootloader?
my partial answer to my own question is that i cant use fastboot commands thru adb, right? but i dont fully know what the heck fastboot is anyway.
also, what about the pdimg15 thing? is that not possible to flash back to stock with pdimg15 if i dont have the 085 bootloader?
anything else i cant do without H085?
acsi007 said:
hmm... what is it specifically that i cant do if i don't flash the engineering bootloader?
Click to expand...
Click to collapse
You cannot flash specific sections of the ROM if something should go south. You cannot flash recovery images via the HBoot, and you cannot flash splash images.
acsi007 said:
my partial answer to my own question is that i cant use fastboot commands thru adb, right? but i dont fully know what the heck fastboot is anyway.
Click to expand...
Click to collapse
fastboot = hBoot = Engineering Screen.
Basically it what allows you to flash items via the Engineering screen. You cannot mount sections of the ROMs, nor can you clear stuff out if you should so choose.
acsi007 said:
also, what about the pdimg15 thing? is that not possible to flash back to stock with pdimg15 if i dont have the 085 bootloader?
Click to expand...
Click to collapse
You can flash the PD15IMG via either recovery image. but it appears that if you use the 3.0.0.5, 3.0.0.6, or the 3.0.2.4 recovery image while trying to flash the PD15IMG (via the HBoot) it will brick your device. So that is not always a fail safe method.
basically the .85 HBoot a BIG tool to help you not brick your device.
thanks so far.. ok, im getting convinced. here's my reference for an eventuality where i'd need to rescue myself from some boot loop and reflash stock
http://forum.xda-developers.com/showthread.php?t=924923
so, in continuing to try to understand recoveries and boot screens here, i saw that after step three in the above thread, it says
"Some times at the end it will boot into fastboot rather then hboot. If this happens just scroll to bootloader and boot into it."
but then you wrote "fastboot = hBoot = Engineering Screen."
so why does the guide say "rather"? (indcating "does not equal")
second, you wrote
"You can flash the PD15IMG via either recovery image. but it appears that if you use the 3.0.0.5, 3.0.0.6, or the 3.0.2.4 recovery image while trying to flash the PD15IMG (via the HBoot) it will brick your device. So that is not always a fail safe method."
"either recovery image" -- you're referring to Clockwork Mod recovery and hboot?
And if you've seen that 3005 - 3024 may brick a PD15IMG flash, then what-- you dont go through Clockwork mod screen at all, you boot into hboot instead?
thanks for slogging thru this so i can get to my "aha!" moment....
acsi007 said:
thanks so far.. ok, im getting convinced. here's my reference for an eventuality where i'd need to rescue myself from some boot loop and reflash stock
http://forum.xda-developers.com/showthread.php?t=924923
so, in continuing to try to understand recoveries and boot screens here, i saw that after step three in the above thread, it says
"Some times at the end it will boot into fastboot rather then hboot. If this happens just scroll to bootloader and boot into it."
but then you wrote "fastboot = hBoot = Engineering Screen."
so why does the guide say "rather"? (indcating "does not equal")
Click to expand...
Click to collapse
when we are talking about booting into Recovery, or the Engineering screen. Fastboot, hBoot, and Engineering screen are all pretty much one in the same. Just like some people call softdrinks, "pop", "soda", or "coke". It's terminology. the reason for the "Some times at the end it will boot into fastboot rather then hboot. If this happens just scroll to bootloader and boot into it." Is even though are in a "bootloader" screen the phone must pick up and recognize that you want to use fastboot. so sometimes, not typical though, you must select the "fastboot option".
acsi007 said:
second, you wrote
"You can flash the PD15IMG via either recovery image. but it appears that if you use the 3.0.0.5, 3.0.0.6, or the 3.0.2.4 recovery image while trying to flash the PD15IMG (via the HBoot) it will brick your device. So that is not always a fail safe method."
"either recovery image" -- you're referring to Clockwork Mod recovery and hboot?
Click to expand...
Click to collapse
Correct there have been several threads popping up that are pointing to people have bricked their devices by flashing the PD15IMG in the Engineering screen but they are using the wrong recovery image. It always said something to the degree of "fail -PU". One guy was able to fix his by flashing the 2.5 recovery image from the Engineering screen then flashing the PD15IMG.
acsi007 said:
And if you've seen that 3005 - 3024 may brick a PD15IMG flash, then what-- you dont go through Clockwork mod screen at all, you boot into hboot instead?
thanks for slogging thru this so i can get to my "aha!" moment....
Click to expand...
Click to collapse
Yes to flash the PD15IMG you need to be in the Engineering Screen. but from reading that other thread you need the 2.5 recovery image to do it.
neidlinger said:
Yes to flash the PD15IMG you need to be in the Engineering Screen. but from reading that other thread you need the 2.5 recovery image to do it.
Click to expand...
Click to collapse
Wow- so I have to get rid of 3024 and flash cwm2545 (or whatever that exact number is) to use the pd15img that's so important to regaining control over a hypothetical borked flash?
acsi007 said:
Wow- so I have to get rid of 3024 and flash cwm2545 (or whatever that exact number is) to use the pd15img that's so important to regaining control over a hypothetical borked flash?
Click to expand...
Click to collapse
i think we are on two different wave lengths.
one of the first Clockwork recoverys that came out where for 2.2 style ROMs, where store information in an EXT3 format. When Google released 2.3 we needed a new recovery image to flash the EXT4 design that the 2.3 ROMs bring. 3.0.0.5 will only handle 2.2 ROMs 3.0.0.6 and 3.0.2.4 will do both.
The problem lies in the fact that EXT3 and EXT4 ROMs store and handle information differently.
using the recovery image while trying to load the PD15IMG will cause the load to fail.
Now if you have the engineering screen loaded you can manually load the 2.5.1.4 recovery image via the Engineering screen then flash the PD15IMG and all should be good.
But this is only if you need to revert back to 100% stock.
we're not on 2 wavelengths, i'm just talking like an inebriated baby on no sleep!
thanks for the patience you display toward everyone, all the while having a guide which spells all this stuff out...
so the file system rules, and since 2.3's obvious big upgrade was the F/S, it borked previous recoveries.
so i'm on CWM3024, the latest, which i installed via rommanager, and it flashed it, and i nandroid backed up.
so im set for ext3 and ext4 incl pd15img, (which is ext3). right?
also, flashing pd15img- that reverts the bootloader from 085 to 086 again?
Um...neidlinger, fastboot and hboot are two totally different things. Keep in mind, I am not picking on you...
Appreciate your enthusiasm, but you are wrong a lot.
kmdub said:
Um...neidlinger, fastboot and hboot are two totally different things. Keep in mind, I am not picking on you...
Appreciate your enthusiasm, but you are wrong a lot.
Click to expand...
Click to collapse
then i'm out....
I tried to root my new nexus s that i got last friday.....
tey must be some thread about this but my english is not in top shape...
i am now stuck at google page when turning on my phone. must be something about my boot....
I live in Canada and my provider is roger here all the information that i found :
in fastboot mode:
product name: herring
hw version : rev 16
bootloader version : i9020xxka3
baseband version : i9020uckb2
carrier info : att
on my box:
model: gt-i9020fsrrwc
Please i realy need help.....
Vbob
Describe steps you have taken to root in detail.
i know this is not the right place to start, but i did't know....
hxxp://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/
i was stock after "fastboot flash boot rootboot.img" i was ubable to reboot
Vbob
any one can help me?
Vbob
Download this first
http://www.mediafire.com/?0pzz830oc0xa0e7
Rename it to rootboot.img and overwrite the one in C:\nexusroot
Try
Code:
fastboot flash boot rootboot.img
again.
ok did it now wen i boot the phone i always get into clockworldmod recovery v3.0.2.5
i want to make sure i dont do something bad, what should i do?
Vbob
thanks for helping me ....
i finely found the way. i have push a update and it work
Thank
by the way, juste to be shure, can you point me to the right way of rooting my phone?
Vbob
im having the same problem with mine.....but where i messed up is that i didnt back anything up after unlocking and now i pretty much have a blank sd card/internal memory.....i have tried lots of methods trying to push a recovery into the phone but nothing has worked
im glad this worked for you
vbobmac said:
thanks for helping me ....
i finely found the way. i have push a update and it work
Thank
by the way, juste to be shure, can you point me to the right way of rooting my phone?
Vbob
Click to expand...
Click to collapse
If you can get into CWM, you only need two more steps now
1) mount /system
2) install zip from sd -> su-2.3.6.1-ef-signed.zip
Reboot and you are rooted.
redlilcivic said:
im having the same problem with mine.....but where i messed up is that i didnt back anything up after unlocking and now i pretty much have a blank sd card/internal memory.....i have tried lots of methods trying to push a recovery into the phone but nothing has worked
im glad this worked for you
Click to expand...
Click to collapse
You need to describe the steps you have taken, and describe the problem with more detail.
If you can get into CWM, you only need two more steps now
1) mount /system
2) install zip from sd -> su-2.3.6.1-ef-signed.zip
Reboot and you are rooted.
Click to expand...
Click to collapse
i did a update yesterday, and now i think i dont have the right system recovery.
now when clicking system recovery, i get a "!" whit the android character...
vbobmac said:
ok did it now wen i boot the phone i always get into clockworldmod recovery v3.0.2.5
i want to make sure i dont do something bad, what should i do?
Vbob
Click to expand...
Click to collapse
Please, I have exactly the same problem. When I boot the phone i always get into clockworldmod recovery v3.0.2.5
How Can I do To unmake this?
Please, somebody can help?
[email protected]_OC said:
Please, I have exactly the same problem. When I boot the phone i always get into clockworldmod recovery v3.0.2.5
How Can I do To unmake this?
Please, somebody can help?
Click to expand...
Click to collapse
So instead of booting into the rom you boot into clockwork recovery?
Sent from my Nexus S using XDA Premium App
reddv1 said:
So instead of booting into the rom you boot into clockwork recovery?
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Yes I follow the root technique of "hxxp://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/", and, like "vbobmac", my phone stock at google page.
After that, i try the "rootboot.img" who give "Si_NZ" to "vbobmac".
And, like him, after that when i boot, i can only boot into clockwork recovery, and i can't go into "bootloader" mode.
Can I make my rom at stock into clockwork recovery?
I hope, it's possible to unmake this mistake?
In the post "[ROM] Stock - 2.3.4 - GRJ22 - Deodexed w/radio for NS/NS4G", do i have to take a rom rooted or not? Because my phone is unlock, but not totally rooted i think.
Sorry for all those questions, but i'm a little lost. And i'm affraid to make an error who will kill my Nexus S.
Thank you a lot for your help, i wait your answer before doing anything.
Thank you again.
It's great to see people, who are ready to help directly.
Edit: Now I can boot in "bootloader" mode, but i try with ODIN to put back at stock my phone, but the computer (Windows 7) dont recognise the phSamsungone.
Even when I install PC Studio 3.
Do you now an other way to make my phone work? Root or at stock, doesn't matter. Just if he can live, it's good to me.
[email protected]_OC said:
Yes I follow the root technique of "hxxp://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/", and, like "vbobmac", my phone stock at google page.
After that, i try the "rootboot.img" who give "Si_NZ" to "vbobmac".
And, like him, after that when i boot, i can only boot into clockwork recovery, and i can't go into "bootloader" mode.
Can I make my rom at stock into clockwork recovery?
I hope, it's possible to unmake this mistake?
In the post "[ROM] Stock - 2.3.4 - GRJ22 - Deodexed w/radio for NS/NS4G", do i have to take a rom rooted or not? Because my phone is unlock, but not totally rooted i think.
Sorry for all those questions, but i'm a little lost. And i'm affraid to make an error who will kill my Nexus S.
Thank you a lot for your help, i wait your answer before doing anything.
Thank you again.
It's great to see people, who are ready to help directly.
Edit: Now I can boot in "bootloader" mode, but i try with ODIN to put back at stock my phone, but the computer (Windows 7) dont recognise the phSamsungone.
Even when I install PC Studio 3.
Do you now an other way to make my phone work? Root or at stock, doesn't matter. Just if he can live, it's good to me.
Click to expand...
Click to collapse
Can you access the sdcard to flash a rom? You can do that by going to clockwork recovery, then mounts and storage, then select mount USB storage, then on your PC go to my computer and press refresh until you see the phone storage appear, keep pressing refresh for atleast 5 minutes because sometimes it takes a while. Then download any rom rooted or unrooted and flash in clockwork recovery.
If you can't do that and you can use fastboot, I'll send you a system.img and boot.img to flash.
Sent from my Nexus S using XDA Premium App
reddv1 said:
Can you access the sdcard to flash a rom? You can do that by going to clockwork recovery, then mounts and storage, then select mount USB storage, then on your PC go to my computer and press refresh until you see the phone storage appear, keep pressing refresh for atleast 5 minutes because sometimes it takes a while. Then download any rom rooted or unrooted and flash in clockwork recovery.
If you can't do that and you can use fastboot, I'll send you a system.img and boot.img to flash.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Yes, i can mount my phone, but when i try to install the default rom, but it's not working. I have an error.
At least the manipulation is working, i can mount on my computer the nexus.
Do you have a rom 2.3.4 for Nexus i9023 please? Maybe i don't flash with a good rom?
Thanks again for your help.
I try again, to flash with the original 2.3.4, but the operation abort everytime.
Do i have an other choice for flashing my phone?
Mount the sdcard is working, copy files work too, and i can run the update.
But, the operation abort with a "statut 7".
[email protected]_OC said:
I try again, to flash with the original 2.3.4, but the operation abort everytime.
Do i have an other choice for flashing my phone?
Mount the sdcard is working, copy files work too, and i can run the update.
But, the operation abort with a "statut 7".
Click to expand...
Click to collapse
You have try and use a new recovery. Download this recovery http://forum.xda-developers.com/showthread.php?t=988686 and flash it in the bootloader and try flashing a rom again.
Sent from my Nexus S using XDA Premium App
reddv1 said:
You have try and use a new recovery. Download this recovery http://forum.xda-developers.com/showthread.php?t=988686 and flash it in the bootloader and try flashing a rom again.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
I flash, like the first time, from Windows "cmd"?
Sorry for all those questions, but i don't want to make something who can kill my phone.
And I think, i don't have the good bootloader.
My phone is a Nexus S i9023, but since i try to root my phone, my bootloader version is the "i9020XXKA3".
You think, i have to change the bootloader first?
For flashing bootloader and clocwork recovery, i have to do it from Windows?
Waiting for your answer.
Thank's a lot
[email protected]_OC said:
I flash, like the first time, from Windows "cmd"?
Sorry for all those questions, but i don't want to make something who can kill my phone.
Click to expand...
Click to collapse
Yes, from cmd, type "fastboot flash recovery recoveryname.img" , replace "recoveryname.img" with what it's named. Good luck.
Sent from my Nexus S using XDA Premium App
reddv1 said:
Yes, from cmd, type "fastboot flash recovery recoveryname.img" , replace "recoveryname.img" with what it's named. Good luck.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
I flash the recovery, and now i have the v4.0.0.2, but i still can't flash a rom.
I still have the same message:
"assert failed: file_getprop("/system/build.prop". "ro.build.fingerprint") == "google/soju/crespo:2.3.2/GRH78C/93600:user/release-keys" ||
file_getprop("/system/build.prop". "ro.build.fingerprint") == "google/soju/crespo:2.3.3/GRI40/102588:user/release-keys"
E: Error in /sdcard/update 2.3.3.zip
(Statut 7)
Installation aborted.
Don't you think it's because my bootloader is not the good one?
Can flash it too, from Windows?
I was using the tool kit here: [NEXUS 4 TOOLKIT V2.0.0]
I got the drivers to work and i unlocked my device then when the root procedure came around my device failed to flash the unsecure boot img.
so i went to download N-Cry's toolkit to root from their. This also refused to work now my phone will not boot. I can get to the google screen with the unlock logo and fastboot.
UnderZone7 said:
I was using the tool kit here: [NEXUS 4 TOOLKIT V2.0.0]
I got the drivers to work and i unlocked my device then when the root procedure came around my device failed to flash the unsecure boot img.
so i went to download N-Cry's toolkit to root from their. This also refused to work now my phone will not boot. I can get to the google screen with the unlock logo and fastboot.
Click to expand...
Click to collapse
try wiping data/factory reset then try to boot.
simms22 said:
try wiping data/factory reset then try to boot.
Click to expand...
Click to collapse
How do i do that?
UnderZone7 said:
How do i do that?
Click to expand...
Click to collapse
do you have a custom recovery installed? you would do it in the custom recovery. if you dont, you might have to flash the factory image via fastboot http://forum.xda-developers.com/showthread.php?t=2010312
doing everything the right way instead of a root toolkit is easier and faster, you just need to do a little reading first.
simms22 said:
do you have a custom recovery installed? you would do it in the custom recovery. if you dont, you might have to flash the factory image via fastboot http://forum.xda-developers.com/showthread.php?t=2010312
doing everything the right way instead of a root toolkit is easier and faster, you just need to do a little reading first.
Click to expand...
Click to collapse
The root part wasn't working so I never go to the flashing recovery
UnderZone7 said:
The root part wasn't working so I never go to the flashing recovery
Click to expand...
Click to collapse
So flash one
UnderZone7 said:
The root part wasn't working so I never go to the flashing recovery
Click to expand...
Click to collapse
as said above, flash one now via fastboot.
the right way to root a nexus in general terms.. fastboot oem unlock via fastboot, flash a custom recovery via fastboot, flash either the su binaries or a custom rom via your new custom recovery, reboot and profit. thats all that needs to be done when using any nexus, thats one reason we buy nexus devices
I don't think people understand what "brick" really means.
Sent from my iPad 4
Know why I love the XDA community so much?
Because after the 1 millionth "I bricked my Nexus, what do I do??" thread with someone who might not have done all the research they should have before flashing their device, XDA will still post helpful advice and generally help out, instead of posting comments like "omg read before you flash!!!".
And as stated above OP, try to stay clear of toolkits and stuff, at least starting out. That way, you learn a lot about what's going on in the background, and learn how you can prevent things from going wrong, and what to do when they do go wrong. I highly recommend reading at least the first 4 posts in this thread. It is extremely helpful.
simms22 said:
as said above, flash one now via fastboot.
the right way to root a nexus in general terms.. fastboot oem unlock via fastboot, flash a custom recovery via fastboot, flash either the su binaries or a custom rom via your new custom recovery, reboot and profit. thats all that needs to be done when using any nexus, thats one reason we buy nexus devices
Click to expand...
Click to collapse
Thank you so much for all your help. I used the guide got fastboot and the drivers working and I was able to flash a rom.