Develop Bugs

[Q] Bricked LTE Galaxy Nexus Help!

Does anyone happen to have a way to flash the stock img in fastboot? I can't find the stock LTE variant anywhere.
I unlocked the bootloader through fastboot, then ran p3Droid's root method for the LTE galaxy nexus, and now the phone will just get stuck at the google logo.
I did manage to install CWM onto the phone, but since there is no SD card, I can't push anything in ADB to the phone. It just gives me an error when I try. If there is anyone who could help, that would be amazing!
More information:
Yes, fastboot commands still work. I have tried flashing various boot.imgs to the phone to no effect such as the one from the nandroid on rootzwiki and also flashing the boot.img from the only LTE ROM on rootzwiki as well.

overlord727 said:
Does anyone happen to have a way to flash the stock img in fastboot? I can't find the stock LTE variant anywhere.
I unlocked the bootloader through fastboot, then ran p3Droid's root method for the LTE galaxy nexus, and now the phone will just get stuck at the google logo.
I did manage to install CWM onto the phone, but since there is no SD card, I can't push anything in ADB to the phone. It just gives me an error when I try. If there is anyone who could help, that would be amazing!
More information:
Yes, fastboot commands still work. I have tried flashing various boot.imgs to the phone to no effect such as the one from the nandroid on rootzwiki and also flashing the boot.img from the only LTE ROM on rootzwiki as well.
Click to expand...
Click to collapse
As simple as it sounds, have you tried booting into recovery and doing a factory reset and clearing your cache?

I have done this many times. Also, CWM keeps throwing an error about the sd card among other things

Have you posted your issue on MDW? P3 may have the necessary files to flash via odin. The files are out there, but people have been strictly instructed to not release them.
Again, I would check with P3 for the fix.
He is not responsible for the issue, but he may be able and willing to help.

Hmm I will post there. I have posted on his forum for something else, but maybe If I make a thread he will notice it

Doesn't the recovery have an option to mount USB storage?
Sent from my Sensation using Tapatalk

It says this, but it wont actually do it. Unless there is something I am missing when I try this. I am connected via the USB to the computer, but nothing pops up.

Just checking in. Have you found a solution yet?
I can tell you that on my VZW Gnex that it will not allow you to transfer files via usb in CWR, as you have stated. Your only hope is a .tar file for Odin. Did you get any reply at MDW?

overlord727 said:
It says this, but it wont actually do it. Unless there is something I am missing when I try this. I am connected via the USB to the computer, but nothing pops up.
Click to expand...
Click to collapse
adb push the files you need to the sdcard

KiNG OMaR said:
adb push the files you need to the sdcard
Click to expand...
Click to collapse
I cant believe I left this one out lol. Good call!

The issue is, I get an error every time I try to push anything to the SD card. I dont know what the problem is. What I really need is a systemimg

Why do people always say their phone is "bricked" when it clearly isn't lol :S

this is why I should wait before rooting. there seems to be no clear solutions available yet.
overlord727 said:
Does anyone happen to have a way to flash the stock img in fastboot? I can't find the stock LTE variant anywhere.
I unlocked the bootloader through fastboot, then ran p3Droid's root method for the LTE galaxy nexus, and now the phone will just get stuck at the google logo.
I did manage to install CWM onto the phone, but since there is no SD card, I can't push anything in ADB to the phone. It just gives me an error when I try. If there is anyone who could help, that would be amazing!
More information:
Yes, fastboot commands still work. I have tried flashing various boot.imgs to the phone to no effect such as the one from the nandroid on rootzwiki and also flashing the boot.img from the only LTE ROM on rootzwiki as well.
Click to expand...
Click to collapse
No worry...you probably soft-bricked it.

Use fastboot to flash CWM. If CWM cannot read the file system, wipe the cache and reboot.
Sent from my Galaxy Nexus using Tapatalk

thrillerbee said:
Use fastboot to flash CWM. If CWM cannot read the file system, wipe the cache and reboot.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I have the same problem, except its a GSM phone, not a LTE Verizon.
I tried wiping the cache clean and rebooting, the phone is still stuck at the google logo screen!
What should I do?!?!?! I'm desperate here...

you should be able to get into ADB mode at some point, to push the file to /data/media (= /sdcard).
If you're seeing CWM recovery mode, then you're fine. ADB would see your phone as ADB-recovery.
When it does, push boot.img, and recovery.img into "/data/media" not "/sdcard/". (There is a permission issue with soft link).
If you succeed pushing the files into your Nexus, the rest is just flashing the files in FASTBOOT.
Your last successul boot had 4.0.2? or 4.0.4? Be sure to match the two files above to the correct version. Otherwise, you'll be stuck with those google logo

Flashed CM9 and stuck in bootscreen help plz

Hey guys i just flashed the 25/05/2012 build of cm9 and for some reason its stuck in the bootscreen and doesnt go past it, i can still go back into cwm recovery or fastboot but what do i do to get my phone working...?
iv been trying to get the new zip files to flash any rom onto it but cant get comp to reconise phone i hope someone can guide me to getting this working

iv tryed a few offical ruu roms and none of them are working aswell, i really dontknow why cm9 i installed how casued this bootloop shame i cant attempt to try the newly updated version for this loop...anyways is there a way to get my phone working

encryptioncsta said:
Hey guys i just flashed the 25/05/2012 build of cm9 and for some reason its stuck in the bootscreen and doesnt go past it, i can still go back into cwm recovery or fastboot but what do i do to get my phone working...?
iv been trying to get the new zip files to flash any rom onto it but cant get comp to reconise phone i hope someone can guide me to getting this working
Click to expand...
Click to collapse
Did you make a NAND backup of your previous ROM ? If so, restore it
Did you try to instal it again? Do it if not
And the last one, did you flash the boot.img ?

no i didnt make a backup and no i didnt have the boot.img file at the time
im super scared to what i can do now...

is there any way i can transfer files from my computer to my phone at this stage?
i have the boot.img and new cm9 files here now but dontknow if theres anyway to get these onto the phone in its current state

encryptioncsta said:
no i didnt make a backup and no i didnt have the boot.img file at the time
im super scared to what i can do now...
Click to expand...
Click to collapse
Dont panic, you dnt bricked it
OK, lets do your job ...
HERE is your boot.img for CM9...flash that first via fastboot and then flash the ROM via CWM.
---------- Post added at 03:43 AM ---------- Previous post was at 03:41 AM ----------
encryptioncsta said:
is there any way i can transfer files from my computer to my phone at this stage?
i have the boot.img and new cm9 files here now but dontknow if theres anyway to get these onto the phone in its current state
Click to expand...
Click to collapse
You dnt have to do that over the CWM, you do that over the fastboot comand: "fastboot flash boot boot.img"

encryptioncsta said:
is there any way i can transfer files from my computer to my phone at this stage?
i have the boot.img and new cm9 files here now but dontknow if theres anyway to get these onto the phone in its current state
Click to expand...
Click to collapse
go download latest recovery (test version) fastboot that. then you can copy a different rom to your storage.

crap...how do i flash it when i cant put it onto the phones internal sd card?
iv had a samsung for way too long its kinda hard so far getting used to htc lol

encryptioncsta said:
crap...how do i flash it when i cant put it onto the phones internal sd card?
iv had a samsung for way too long its kinda hard so far getting used to htc lol
Click to expand...
Click to collapse
You dnt put the boot.img on your phone, you put that file in the fastboot folder on your PC .

I think the kernel is incompatible. If that's not the case then the rom is at fault. It is after all... still in testing. So I recommend a 1 click install from Odin. I had worst before where it wouldn't let me even boot into recovery and the one clicker saved me
Sent from my SPH-D710 using xda premium

It could also be because u didn't properly wipe. And it overlapped the current from therefore giving u errors
Sent from my SPH-D710 using xda premium

i kls i flash the boot via cmd but so far still wont boot, where can i get the latest boot image that lets me use my pc as a storage device

also how do i flash using odin?
i cant get odin to reconise the htc one x but it will pickup my galaxy note

encryptioncsta said:
i kls i flash the boot via cmd but so far still wont boot, where can i get the latest boot image that lets me use my pc as a storage device
Click to expand...
Click to collapse
flash the ROM again and then the boot.img befor you let the ONE X boot ...

i just tryed flashing the rom again and then flashed the boot.img but still hangs at the bootloop

encryptioncsta said:
i just tryed flashing the rom again and then flashed the boot.img but still hangs at the bootloop
Click to expand...
Click to collapse
Did you look into the zip file ? Maybe you first had to extract it and then pic the right zip ? Open the zip on your PC and tell me the first 2 files you see there ...

dude, go here and get the test recovery http://forum.xda-developers.com/showthread.php?t=1594819
then get a different rom boot into recovery & connect your usb cord. when htc storage pops up on your pc put the new rom on your storage. flash it then boot to bootloader and flash its boot.img . this time check the md5 sum before you flash. the one you have now probably didn't download correctly.

what do u mean by md5?
i have given up with this cm9 crap already, i tryed trip version of cm9 but nothing with work as in no bluetooth no wifi no web broswer would work and even sound thats why i finally wanted to try this version over here at xda and now i cant seem to get any rom to work lol

encryptioncsta said:
what do u mean by md5?
i have given up with this cm9 crap already, i tryed trip version of cm9 but nothing with work as in no bluetooth no wifi no web broswer would work and even sound thats why i finally wanted to try this version over here at xda and now i cant seem to get any rom to work lol
Click to expand...
Click to collapse
md5 is a checksum to validate downloading wen't correctly. You might want to take a few min to calm down and do some reading on what your actually doing before messing with a $700 phone There are even threads here that show you how to flash roms correctly, How to recover from bad flashes etc. I'm not trying to be a ****, but Seriously there are 400 threads identical to this one & every one of them ends the same way. Plz follow the instructions given to you earlier & push the test recovery so you can mount your usb drive. then flash a different Rom, any rom. & you will be ok. Just don't freak out, I think we've all been in this position before. But there is always a way to recover.

i managed to flash trips version of cm9 back on it bit its really unstable and so many features dont work, so how should i go about installing either this cm9 version or another custom rom?
also whats the best rom available atm? i kinda prefere stock ics look but open minded as i just want all features working rather than caring about looks

Did I brick my Galaxy s3?

Well.. in a nutshell, I installed CWM recovery, rooted the phone by installing the update from the "SD Card" when it was really the phone's internal memory, and all worked well. The original idea was to edit some .prop file in /system through a root file explorer. Basically, I changed a value as one stupid tutorial suggested which ended up causing the phone to boot in to a black screen. The phone goes in to recovery and D/l mode, but the problem is flashing ANY type of ROM to the phone. Odin is useless because you can only attach .tar, .gzip, .smd,... etc.. and the roms are usually in a .zip format. This means I need to get the .zip rom on to the phone's "Sd card" which is just internal memory and should clearly specify so. I can't exactly access my phone's memory afaik since.. you know.. the phone doesn't have any OS to boot up.
Now what is it that I can do to get a rom on the phone? Android commander is another useless program right now, also. Aside from the program always telling me my rooted phones aren't rooted, the program doesn't even detect the phone while it's in dl mode, recovery mode, bricked mode, garabge mode,... you get the point. I'm just a little irritated after trying for two days to get in to my own internal storage. If anyone has anything to share, and decides to share it, thanks a lot.

bump it would be nice for someone to help....

Nothing is flashing because you changed the ro.build props. There are stock Odin roms floating atound, or you can remove the device check from the updater script in the zips you download and then try to flash.
Sent from my SGH-T999 using xda premium

Or if you have adb you can push back stock build prop back to /system
Sent from my SGH-T999 using xda premium

All these suggestions I read on googled pages from people having similar issues are just such perfect ideas. I wish they worked, though. I have tried pretty much everything.
Since my last post I:
- Wiped every cache you can dream of
- Flashed boot-stock-tmobile-sgh-t999 probably 4 different times, and did the above step after each failure.
- Tried every possible way to get in the "external sd card" meaning "my phone's internal memory"
- Tried pulling the build.props, however without a valid operating system, I'm not going to get very far.
- Looked ALL OVER the internet for a STOCKY RECOVERY ROM in a .tar format. I don't see why it's too much to ask to be able to simply flash a rom from the pc odin since I'm pretty sure I won't be using odin mobile without first getting adroid booted up some how.
Yes, I disabled auto reboot in odin, I've tried pretty much everything and I really don't know where else to turn.

In android updater scripts there is a check into make sure you're flashing the correct phone. If the file is missing, it's going to fail this check and not flash.
If you unzip a Rom and modify this it should work.
On second thought,
You should follow the thread about returning to stock. That has an Odin flash able image that should get you booting again and then you can restart the process to root your phone.
Sent from my SGH-T999 using xda premium

I had that same problem I was only able to go to download mode so I used Odin and flashed stock tmo file to unroot the phone I can't remember exactly what it was called and it worked just fine and now I'm rooted again on cm10 and it works perfectly
Sent from my SGH-T999 using xda app-developers app

boot into recovery with the phone plugged into your computer. then open cmd (if in windows) and cd to the directory with a different rom then do
adb push xxx.zip /sdcard/
wait for it to finish then reboot recovery and flash the rom.

jellydroid13 said:
boot into recovery with the phone plugged into your computer. then open cmd (if in windows) and cd to the directory with a different rom then do
adb push xxx.zip /sdcard/
wait for it to finish then reboot recovery and flash the rom.
Click to expand...
Click to collapse
It's failing getprop ro.build.device
It's gonna do that even with pushing a new Rom to the sdcard unless those lines are removed from updater script.
Sent from my SGH-T999 using xda premium

similar problem, but long story short I can't boot into recovery and flashing through ODIN gets me an "unsupport dev_type" message and no results. Any suggestions?

The super obvious suggestion is to just restore your nandroid backup. Before any mod always make one that's in good shape. Every guide tells you to do this but you didn't mention it. Did you not make one? If you can get into recovery and/or DL mode then I'm pretty sure you are not bricked though.

the-Mike_D said:
If you can get into recovery and/or DL mode then I'm pretty sure you are not bricked though.
Click to expand...
Click to collapse
exactly. something's not being done right.

dyuhas1 said:
similar problem, but long story short I can't boot into recovery and flashing through ODIN gets me an "unsupport dev_type" message and no results. Any suggestions?
Click to expand...
Click to collapse
After seeing this OP, are you saying you can NOT get into d/l mode? also, look under devices on win machine, do you see an entry QLOAD*** if so you can NOT and will not get to d/l mode. It is hard bricked. time to get a jtag service. Stop wasting time looking for an answer and get it fixed. again, if you can not get into d/l mode, this is my suggestion. I HAVE BEEN THERE, DONE THAT. BTW, I have the usb jig, IT WILL NOT WORK on hard brick. hehe used it several times on soft bricks though.
Good luck.

Here is a French company doing that rescue service for bricked Galaxy S3 by JTAG
Réparer brick Galaxy S3

Wow, here is a quick and fast service. Get the usbjiig also for future soft-bricks.
MobileTechVideos.COM
http://mobiletechvideos.mybigcommerce.com/

help phone is not booting

yesterday i was in the franco kernel updater app and i saw a new nightly to i wanted to flash it but by mistake i looks like flashed milstone version so the device got root access to restart the device and flash the kernel
but the device rebooted to stuck at Google logo for 15min so i pulled out the battery re-insert it and press the power button and nothing happens still stuck at Google logo with no boot loop or restarting it self
i can get to CWM and fastboot but when i start the device its stuck at that :crying:
my phone is on that way since yesterday and i cant leave it like this for longer time since iam travailing nor can i wipe every thing on it and get a fresh start cuz i do have important things on the sdcard
plz help
i do believe its a kernel related issue but what can i do ?? i cant push a .zip kernel to flash it in CWM

jik saw said:
yesterday i was in the franco kernel updater app and i saw a new nightly to i wanted to flash it but by mistake i looks like flashed milstone version so the device got root access to restart the device and flash the kernel
but the device rebooted to stuck at Google logo for 15min so i pulled out the battery re-insert it and press the power button and nothing happens still stuck at Google logo with no boot loop or restarting it self
i can get to CWM and fastboot but when i start the device its stuck at that :crying:
my phone is on that way since yesterday and i cant leave it like this for longer time since iam travailing nor can i wipe every thing on it and get a fresh start cuz i do have important things on the sdcard
plz help
i do believe its a kernel related issue but what can i do ?? i cant push a .zip kernel to flash it in CWM
Click to expand...
Click to collapse
what rom zip files do you have on your sdcard.

thanked for error.
tried flashing a boot.img via fastboot?standard or from another dev's kernel not in AK format (zimage)
or
tried flash another rom that you have zip inside phone?if you dirty flash,you simple don't loose anything..and the boot.img it's reflashed.
WRONG SECTION;READ THE RULES

jik saw said:
yesterday i was in the franco kernel updater app and i saw a new nightly to i wanted to flash it but by mistake i looks like flashed milstone version so the device got root access to restart the device and flash the kernel
but the device rebooted to stuck at Google logo for 15min so i pulled out the battery re-insert it and press the power button and nothing happens still stuck at Google logo with no boot loop or restarting it self
i can get to CWM and fastboot but when i start the device its stuck at that :crying:
my phone is on that way since yesterday and i cant leave it like this for longer time since iam travailing nor can i wipe every thing on it and get a fresh start cuz i do have important things on the sdcard
plz help
i do believe its a kernel related issue but what can i do ?? i cant push a .zip kernel to flash it in CWM
Click to expand...
Click to collapse
Try restoring from nand backup or reinstall the ROM
Sent from my Galaxy Nexus using xda premium

As nexxusdev is implying, just flash your ROM again.
Sent from my Galaxy Nexus using xda premium

nexxusdev said:
what rom zip files do you have on your sdcard.
Click to expand...
Click to collapse
i have none not even the kernel zip file
sert00 said:
thanked for error.
tried flashing a boot.img via fastboot?standard or from another dev's kernel not in AK format (zimage)
or
tried flash another rom that you have zip inside phone?if you dirty flash,you simple don't loose anything..and the boot.img it's reflashed.
WRONG SECTION;READ THE RULES
Click to expand...
Click to collapse
i will try to flash boot.img from another kernel and will see what happens
and i dont have any flash zip files in my sd card but i learned the lesson i will always leaves a kernel zip and rom zip file in case
and sorry for that but i was in hurry my primary phone is messed up
Chance Ill said:
Try restoring from nand backup or reinstall the ROM
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
iam on stock JB
obtained said:
As nexxusdev is implying, just flash your ROM again.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
its stock JB rom flashed it over with galaxy nexus toolkit and downloaded the rom from google's site so its not a zip flashable
thanks all for replys and sorry for thw wrong section

im not sure but i remember on my g2x you could hook up phone from recovery mode and mount it on the computer with sd card .. have you looked around in CWM? This is your fault to be honest you deserve this for not making a NAND back up. ALWAys MAKE A BACK UP! period. There is a reason why devs and everyone else stress' it so much.

Sert00 is right. Flash any [previously] working ROM on it. It will be a dirty flash and some stuff won't work, but you'll be able to backup your data. You'll reflash again later
ed116 said:
im not sure but i remember on my g2x you could hook up phone from recovery mode and mount it on the computer with sd card .. have you looked around in CWM? This is your fault to be honest you deserve this for not making a NAND back up. ALWAys MAKE A BACK UP! period. There is a reason why devs and everyone else stress' it so much.
Click to expand...
Click to collapse
Unfortunately, at least with these beta realeases of JB, usb mount via recovery almost never work.
Try what sert00 told you.

jik saw said:
yesterday i was in the franco kernel updater app and i saw a new nightly to i wanted to flash it but by mistake i looks like flashed milstone version so the device got root access to restart the device and flash the kernel
but the device rebooted to stuck at Google logo for 15min so i pulled out the battery re-insert it and press the power button and nothing happens still stuck at Google logo with no boot loop or restarting it self
i can get to CWM and fastboot but when i start the device its stuck at that :crying:
my phone is on that way since yesterday and i cant leave it like this for longer time since iam travailing nor can i wipe every thing on it and get a fresh start cuz i do have important things on the sdcard
plz help
i do believe its a kernel related issue but what can i do ?? i cant push a .zip kernel to flash it in CWM
Click to expand...
Click to collapse
fastboot is all you need. find a stock rom and flash
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache ???
fastboot erase data
this should work

thank u guys soooooooooooooooooooooooooooooooooooo much
iam very very very very great full to all of u for ur help and for giving me some ideas
i have solved it by extract the .tar imge file that i downloaded from here
and searched for the boot.img file flashed it over galaxy nexus toolkit and now the device restarted and android is upgrading 156 app lol
thanks again and sorry for the wrong section and hey .... why not editing the thread to make it a helpful guide to those who brick their phones like what i just did

djjonastybe said:
fastboot is all you need. find a stock rom and flash
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache ???
fastboot erase data
this should work
Click to expand...
Click to collapse
he didn't want to lose anything...also the data of apps
@jig saw
happy to read that!and from now on,leave inside the phone all the stuff you could need in case similar to what happened you!cheers!:laugh:

sert00 said:
he didn't want to lose anything...also the data of apps
@jig saw
happy to read that!and from now on,leave inside the phone all the stuff you could need in case similar to what happened you!cheers!:laugh:
Click to expand...
Click to collapse
no thank god i didnt lose any thing and the OS is operating normal
i really appreciate that mate
and lesson well learned i'm making folder in the sdcard for buck up stuff
cheers ^_^

Xperia S wont boot or anything

Hi.
Today I received my Xperia S and immediately started rooting it. First i unlocked my bootloader succesfully with help of sonys official tutorial.
Then I rooted my stock ICS 2.45 firmware succesfully with root witch restore binaries thingy. Then I started installing CWM and used ten thousand different tuts and finally succeeded to boot to CWM based recovery v5,5,0.4 with help of THIS TUT
Now it booted to that recovery and then tried to flash FXP205-cm-10-201-302-01-UNOFFICIAL-anzu.zip that with it from internal sd. It did say something about status 7 installation aborted. There were tutorial that said that download FXP205-cm-10-201-302-01-UNOFFICIAL-nozomi.zip but i thought that anzu.zip was newest. Was that a mistake and is there any hope that my xperia s will work ever again?:crying:

Maybe stupid, but didyou fully charged?
LB or UB?
Tried again step by step, maybe u missed something?
FlasTool is ur friend!
Sent from my LT26i using xda app-developers app

Odp: Xperia S wont boot or anything
It's sad but there might be no hope for your Phone since nozomi is the codename for Xperia S and anzu i totalny different model so you flashed wrong kernel so your Phone might be perbricked. Anyways try flashing stock Rom through flashtool. It might work. If you're not able to boot into fastboot/flashmode then your Phone is permanently dead.
Sent from my Xperia S using xda app-developers app

mracer164 said:
It's sad but there might be no hope for your Phone since nozomi is the codename for Xperia S and anzu i totalny different model so you flashed wrong kernel so your Phone might be perbricked. Anyways try flashing stock Rom through flashtool. It might work. If you're not able to boot into fastboot/flashmode then your Phone is permanently dead.
Sent from my Xperia S using xda app-developers app
Click to expand...
Click to collapse
dont be dramatic, get sony's official flashtool and flash back a stock rom, then restart from scratch.
1: download the CM you want but it must be with codename nozomi in it
2: if its cm10 get jellybean 4.1.2 gapps, if its cm9.1 get 4.0.4 gapps,
3: place the files through the stock rom back on your sd card
4: flash the boot.img located in the cm file you downloaded,start your phone in fastboot, then:fastboot flash boot boot.img
5: fastboot reboot
6: wipe cache, dalvik, factory reset and format system(optional) in cwm
7:instal cm zip in cwm
8: install correct google apps zip
9: reboot the device
10: enjoy
methode works for nearly every ROM around here
Sent from my Xperia S using xda app-developers app

Odp: Xperia S wont boot or anything
If he's not getting any leds then situation might be dramatic but if he can reach fastboot/flashmode then there is high chance to get a Phone alive.
Sent from my Xperia S using xda app-developers app

Thankyou guys I finally mamaged to flash the nozomi cm10, i think i had luck.

Again big problem. Now I am in cwm, or fastboot and flashtool (emma). if i type to cmd fastboot devices it shows my device but flashtool and adb device wont show anything. i am trying to push my rom to sd because i did forgot to but in, and already formated system in cwm. Because th pac jellybean rom tut said that i have to format it. help i have no idea what to do now.:crying:

HighVoltage_ said:
Again big problem. Now I am in cwm, or fastboot and flashtool (emma). if i type to cmd fastboot devices it shows my device but flashtool and adb device wont show anything. i am trying to push my rom to sd because i did forgot to but in, and already formated system in cwm. Because th pac jellybean rom tut said that i have to format it. help i have no idea what to do now.:crying:
Click to expand...
Click to collapse
Highvoltage,
You are making all to quick and without attention, too much mistakes for such a short notice.
You don't yet know the process, why don't you lock your Bl and try some custom roms for it? That way you can practice the method and will have almost no chance to hardbrick your phone.
You have your phone alive at this moment or not?
In each case, start from scratch, go to flashtool and go for stock rom again.
Sent from my LT26i using xda app-developers app

Hold on? So u have a pac rom zip on your sd still? If so just flash it
Sent from my Android 4.2.1 Xperia S

Yes, I managed to get it work with adb. i installed zip in cwm with sideload and I think that wasnt succesful so then pushed zip file to sdcard with adb and flashed it again. My biggest problem was finding working usb drivers. I tried about 15 different ways to install drivers but then just downloaded just some random driver and it worked
no time to explain right now because I am at work. Sry for messy text. Will update this post soon