Related
I have been reading threads here and I can't find an answer to my question.
I have an ATT Captivate running ATT 2.2. I ran the super one click app and have superuser available for the apps. I have rom manager free edition but no matter what I try I cannot get it to flash the Clockworkmod Recovery. When I try to flash it I get the message that it's been succesfully downloaded but never get the succesful flash.
I've spent a big part of the day at this and can't figure out why this isn't working. ANY ideas would be appreciated.
TIA, Jeff
[email protected] said:
I have been reading threads here and I can't find an answer to my question.
I have an ATT Captivate running ATT 2.2. I ran the super one click app and have superuser available for the apps. I have rom manager free edition but no matter what I try I cannot get it to flash the Clockworkmod Recovery. When I try to flash it I get the message that it's been succesfully downloaded but never get the succesful flash.
I've spent a big part of the day at this and can't figure out why this isn't working. ANY ideas would be appreciated.
TIA, Jeff
Click to expand...
Click to collapse
It won't actually be flashed to your device. It creates an update.zip file on your internal sd card. What you have to do to get into clockwork is turn your phone off, hold down vol up+vol down+power until you see the AT&T logo show up on the screen. When you see the logo show up, release power but keep holding the volume keys. This will take you into the regular stock recovery. Once you are there, select the 'reinstall packages' option. The phone should reboot, at which point, hold down the volume keys again to get back into the stock recovery. Once it boots into stock recovery for the second time, select 'reinstall packages' again and it should put you into clockworkmod this time around.
At one time in all my trying I've been thru this as well. When I select reinstall packages I get:
E: Failed to verify whole-file signature
E: signature verification failed
Installation aborted
I really want to get away from this ATT 2.2. I waited for the ATT upgrade but since it still won't support bluetooth voice dial I'm going to go this route if I can get it to work.
Jeff
modest_mandroid said:
It won't actually be flashed to your device. It creates an update.zip file on your internal sd card. What you have to do to get into clockwork is turn your phone off, hold down vol up+vol down+power until you see the AT&T logo show up on the screen. When you see the logo show up, release power but keep holding the volume keys. This will take you into the regular stock recovery. Once you are there, select the 'reinstall packages' option. The phone should reboot, at which point, hold down the volume keys again to get back into the stock recovery. Once it boots into stock recovery for the second time, select 'reinstall packages' again and it should put you into clockworkmod this time around.
Click to expand...
Click to collapse
Beg to differ. He has 2.2. Signature verification error.
Sent from my GT-I9000 using XDA App
Recovery 3E. The fix is in the dev forum
Sent from my HTC Vision
http://forum.xda-developers.com/showthread.php?t=909213
Sent from my GT-I9000 using XDA App
Oh right, totally forgot about that. It's been forever since I've flashed stock 2.2.
You can either follow the guide here:
http://forum.xda-developers.com/showthread.php?t=909213
Or you can simply flash back to 2.1 using this and do what I said in my original post:
http://forum.xda-developers.com/showthread.php?t=751518
Pirateghost said:
Recovery 3E. The fix is in the dev forum
Sent from my HTC Vision
Click to expand...
Click to collapse
+1
I've answered the same question atleast 20 times last week.
Please look around the forum and you'll find your answers!
Thanks Pirate for taking care of this one (with so many more to come )
BWolf56 said:
+1
I've answered the same question atleast 20 times last week.
Please look around the forum and you'll find your answers!
Thanks Pirate for taking care of this one (with so many more to come )
Click to expand...
Click to collapse
bets on number of posts this week regarding this same issue?
Good place for this question would be q&a, next time post there or search first.
Sent from a super smooth captivate running andromeda
Pirateghost said:
bets on number of posts this week regarding this same issue?
Click to expand...
Click to collapse
I got $5 on 7, what kind of odds am I looking at?
studacris said:
I got $5 on 7, what kind of odds am I looking at?
Click to expand...
Click to collapse
I got her under, what's the spread?
Sent from a super smooth captivate running andromeda
studacris said:
I got $5 on 7, what kind of odds am I looking at?
Click to expand...
Click to collapse
lolol
I say 11!
Wouldnt it just be easier to load a kernal tar file in odin? I know that may noy be recommended for noobs but im willing the help out walking someone through steps,if you havent already figured it out
Sent from my GT-I9000 using XDA Premium App
brd912 said:
Wouldnt it just be easier to load a kernal tar file in odin? I know that may noy be recommended for noobs but im willing the help out walking someone through steps,if you havent already figured it out
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
It is a way to do it but Odin can easely brick a phone if not used right.
It's alot easier to just prompt the command (.bat) from our computer with our phone plugged in debugging mode and let it do its magic. Takes a few seconds and it's done
Hi,
As most of you probably already know by now, I have released a fully functional nvflash for Transformer yesterday
More information is available at http://androidroot.mobi/2011/06/13/nvflash-on-asus-transformer/
UPDATE 15-06-2011:Bumble-Bee (Apache14) is just as much to thank for this as me! Both of us (from AndroidRoot.Mobi) have worked hard on making this happen! Thanks to Roach for providing the nvflash-ready Prime 1.4 ROM!
UPDATE: The Prime 1.4 linked is European (WW) build! Roach will release 1.5 soon probably and there'll be both WW and US available. I'm planning to write a quick guide on how to root when running stock 3.1 already (it's pretty easy!)! E.g. to stay on full stock and *just* have root
Windows nvflash
Linux nvflash
Quick guide to unbricking:
Connect cable to computer and turn device on while holding down Volume Up. Screen will stay off, but USB will come on.
(Windows only) Find “APX” device in Device manager and update driver, then point it at usbpcdriver directory from the zip
Run download.sh (linux) or download.bat (windows)
???
Profit
Awesome! Thanks a lot!!
rayman84 said:
Hi,
As most of you probably already know by now, I have released a fully functional nvflash for Transformer yesterday
More information is available at http://androidroot.mobi/2011/06/13/nvflash-on-asus-transformer/
Windows nvflash
Linux nvflash
Quick guide to unbricking:
Connect cable to computer and turn device on while holding down Volume Up. Screen will stay off, but USB will come on.
(Windows only) Find “APX” device in Device manager and update driver, then point it at usbpcdriver directory from the zip
Run download.sh (linux) or download.bat (windows)
???
Profit
Click to expand...
Click to collapse
WOW, It's "just like that"? Really that's all what you have to do to unbrick a device? I guess times when flashing roms was dangerous have passed
Great job
Very thanks and keep up the good work!!!
unbrick tool came before root tool. lol
but it's a very useful program for all of us.
thanks for this!
i have a question though, my Samsung Vibrant was HARDWARE LOCKED, which makes button combinations to enter recovery/download modes impossible.
Is there any possibility that my TF has a hardware lock too which will prevent me from accessing the USB when it gets bricked?
i have experience in rooting and/or jailbreaking but i havent rooted my TF yet, coz the only way to root right now is kind of "not layman friendly". and i hate the terms BLOBS. lol
thank you.
So I'm rooted running prime 1.4 could some one explain in laymans terms what difference this makes to me and what if anything I need to do to benefit to my TF
DESIRE HD using leedroid. ASUS TRANSFORMER using prime
atlaswingpasaway said:
unbrick tool came before root tool. lol
but it's a very useful program for all of us.
thanks for this!
i have a question though, my Samsung Vibrant was HARDWARE LOCKED, which makes button combinations to enter recovery/download modes impossible.
Is there any possibility that my TF has a hardware lock too which will prevent me from accessing the USB when it gets bricked?
i have experience in rooting and/or jailbreaking but i havent rooted my TF yet, coz the only way to root right now is kind of "not layman friendly". and i hate the terms BLOBS. lol
thank you.
Click to expand...
Click to collapse
Either you didn't read the post or you might be dyslexic. If you unbrick your device you're pushing a custom ROM which means you automatically get root.
combat goofwing said:
So I'm rooted running prime 1.4 could some one explain in laymans terms what difference this makes to me and what if anything I need to do to benefit to my TF
DESIRE HD using leedroid. ASUS TRANSFORMER using prime
Click to expand...
Click to collapse
You don't need this your already rooted. This is a easy way to root and it can also revive bricks, custom flash different partitions and who knows what other functions can be done with nvflash.
Sent from my HTC Vision using XDA Premium App
Will this wipe your data partition if using this to get a rooted custom rom on?
seshmaru said:
Either you didn't read the post or you might be dyslexic. If you unbrick your device you're pushing a custom ROM which means you automatically get root.
Click to expand...
Click to collapse
it might be both! lol sorry my bad.
im new to tablet/honeycomb rooting so i dont know much about this.
so... im on stock 3.1 right now (i guess the build number wont matter anymore?)
and no root. should i just follow the OP instructions or what?
Canadoc said:
Will this wipe your data partition if using this to get a rooted custom rom on?
Click to expand...
Click to collapse
Using the script included it will wipe all user data. But it may be tweaked later.
Sent from my HTC Vision using XDA Premium App
atlaswingpasaway said:
it might be both! lol sorry my bad.
im new to tablet/honeycomb rooting so i dont know much about this.
so... im on stock 3.1 right now (i guess the build number wont matter anymore?)
and no root. should i just follow the OP instructions or what?
Click to expand...
Click to collapse
Yes if u want a custom rom with root. No more downgrading firmwares anymore like before
Cannot mount SD card in clockwork mod?
EDIT: Nevermind. I tried a different microsd card and it worked fine. False alarm... Move along... nothing to see here
I used the NVFlash utility to flash Prime 1.4 without a hitch but now that I'm trying to deploy the overclock kernel clockwork mod is not playing nice. I get an error E: Can't mount /sdcard when trying to choose a zip file. My understanding is that /sdcard is not the microsd anyway. How do I resolve this? I already tried reformatting the microsd card on my pc but that didn't solve the issue.
Thanks!
-Matt
I thought /Removable/sdcard/ was the sdcard.
Sent from my HTC Vision using XDA Premium App
david279 said:
I thought /Removable/sdcard/ was the sdcard.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
/Removable/MicroSD/ is the MicroSD card slot on the TF104
/SDCard is the 30gigs on the 32gb NAND
Also check the CWM installed. If it's the old one it erases your sd card and internal card on data wipes. You don't want that.
Sent from my HTC Vision using XDA Premium App
david279 said:
I thought /Removable/sdcard/ was the sdcard.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
It's /Removable/MicroSD
But I think the key thing here is that /sdcard is whatever the booting process mounts as /sdcard. This is why CWM has no problem listing the zip files for ROMs, etc. as being from the sdcard. It has accessed it through the actual block device which doesn't change. The whole internal sdcard that we see is some trickery that allows us to have access to all the space on our internal memory, but CWM doesn't know or care about that.
Sent from my Transformer TF101 using XDA Premium App
So...
No rooting, and no CWM..
Just use the tools and profit?
It flashes CWM for future flashing fun.
Sent from my HTC Vision using XDA Premium App
i just dont seem to get it.. . so does this give my stock 3.1 root?
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
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
Greetings,
My name is Tim and I'm looking for some assistance with getting CM 10.1.3 up and running on my GS3 (d2vzw / SCH-i535). I'm not a complete noob, as I managed to successfully flash CM to my Galaxy Tab 2 10.1, and my Droid X2 after countless hours of reading through XDA forum posts for each of the devices, however...I'm still pretty new to a lot of this stuff as I usually don't mess with it once I get CM up and running, and struggle with command prompts still, so I apologize for any/all idiocy posted herein.
I am using the instructions found on the CM site under the d2vzw device (I'd link you but it doesn't appear as though I'm allowed to), and after reading that I don't need to root my device to install CM, I'd prefer to stick with this method (I'm also uncomfortable using Odin or any other such software, as I've heard bad things and already managed to soft brick my GS3 once with it.)
I've got all the appropriate files listed at the above page, but I'm confused with several aspects of the "official" install instructions, and would like some clarification, if possible. Any assistance would be greatly appreciated.
1) USB drivers: I installed the Samsung drivers, but when I ran heimdall print-pit in CMD, it failed giving me an error 12 (can't remember what, specifically, but apparently it has to do with USB drivers). A bit of Google-ing, and I was able to determine that Samsung drivers = bad. Okay, I can deal with that and have uninstalled them. However, does that mean I need to NOT let Windows 7 Update auto install drivers? Further, do I need to use the zadig app to install drivers before I can use Heimdall appropriately? I ask because after I uninstalled the Samsung drivers and rebooted, I tried to flash but it failed.
2) Wording of CMD commands confuses me. Heimdall flash --ABOOT aboot.mbn - okay, I get that I'm typing "heimdall flash" as the preface, but the actual aboot.mbn file is within a .tar file...so do I just flash to the location of the actual tar file? Or do I extract it with 7zip (as I initially tried) and try to flash to the location of the actual aboot.mbn file? Further, --ABOOT doesn't show up on the list of viable options within CMD, which confuses me (is it part of the command, or is it a place holder for some command I'm not understanding).
3) Same question for the other CMD commands.
I've looked around on XDA, the Heimdall site, and elsewhere for more detailed "official" install guides, but they all seem to either involve Odin or rooting, and as I mentioned I want nothing to do with either of them, if possible.
Thank you kindly for your time.
Sure you can do all that, but there are some easy one click root apps for the gs3. Then install cwm recovery. Then flash CM and GAPPs.
Just search the forum and you should be able to find the thread.
Good luck!!
Sent from my SCH-I535 using xda app-developers app
stolo said:
Sure you can do all that, but there are some easy one click root apps for the gs3. Then install cwm recovery. Then flash CM and GAPPs.
Just search the forum and you should be able to find the thread.
Good luck!!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
The only "one-click app" I know of is Framaroot which does not work on the VZW varient of the GS3. So what app are u referring to?
Sent from my SCH-I535 using Tapatalk
I was not referring to an apk on the phone, meant pc app.
I have not personally used this, but looks like it will do the trick.
http://forum.xda-developers.com/showthread.php?t=2332825
stolo said:
I was not referring to an apk on the phone, meant pc app.
I have not personally used this, but looks like it will do the trick.
http://forum.xda-developers.com/showthread.php?t=2332825
Click to expand...
Click to collapse
I thought I downloaded that before and it ended up being a jumble of files...but I just downloaded it now and it looks promising. Thanks for the suggestion, I'll give it a try tomorrow!
Swatpro004 said:
I thought I downloaded that before and it ended up being a jumble of files...but I just downloaded it now and it looks promising. Thanks for the suggestion, I'll give it a try tomorrow!
Click to expand...
Click to collapse
If you want just go try out the cyanogenmod installer from the play store. It should root, unlock, and install for you. Just follow the instructions in the app.
Sent from my AOSP on Grouper using Tapatalk HD
Well, I just tried using the "casual" root one-click thing.
I successfully rooted, but it took ~10 minutes on the flashing of aboot. It claimed to be done, but when I tried to flash CWM it rebooted into the "unauthorized software, contact verizon" screen.
Any ideas? This makes me sad. I don't know why this is so much more difficult than my other devices.
-e- I can still get into download mode, but when I try to go into recovery it just loops back to the main samsung screen with the custom icon and then hops into the verizon unauthorized stuff. Also, when I plug it in to charge it just vibrates once every ~5 seconds without doing much else.
Additionally, I still don't know which USB drivers I want for doing all of this. I'm relying on the ones Windows 7 auto-installs currently, if that helps with troubleshooting. Thank you in advance, again.
Swatpro004 said:
Well, I just tried using the "casual" root one-click thing.
I successfully rooted, but it took ~10 minutes on the flashing of aboot. It claimed to be done, but when I tried to flash CWM it rebooted into the "unauthorized software, contact verizon" screen.
Any ideas? This makes me sad. I don't know why this is so much more difficult than my other devices.
-e- I can still get into download mode, but when I try to go into recovery it just loops back to the main samsung screen with the custom icon and then hops into the verizon unauthorized stuff. Also, when I plug it in to charge it just vibrates once every ~5 seconds without doing much else.
Additionally, I still don't know which USB drivers I want for doing all of this. I'm relying on the ones Windows 7 auto-installs currently, if that helps with troubleshooting. Thank you in advance, again.
Click to expand...
Click to collapse
you just didn't unlock your bootloader that's all. Flash stock (or stock recovery) using Odin. Then root using the same method above. When rooted unlock your bootloader using EZunlock1.2. Its an app that runs on your phone. Then flash recovery. Done.
Edit: at this point it may be easier to just flash a prerooted stock ROM using Odin.
Sent from my SCH-I535 using Tapatalk
Sandman-007 said:
you just didn't unlock your bootloader that's all. Flash stock (or stock recovery) using Odin. Then root using the same method above. When rooted unlock your bootloader using EZunlock1.2. Its an app that runs on your phone. Then flash recovery. Done.
Edit: at this point it may be easier to just flash a prerooted stock ROM using Odin.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Thank you, Sandman. I will try this right now.