i need some files from a working phone to try to unbrick mine - LG Nitro HD

hey
long story short, i bricked my nitro hd by mistake while going back to stock (typo error in dd command) and i need some files from a working phone to attempt a last attempt to save it before i send it to Jtagging service.
there is a small program in this thread that will collect all the bootloaders i need (it needs root access)
if you're in windows you should run backup.bat from Brixfix-2-1.zip.
if you're in linux then you should run get-part.sh and getpartbin.py
thanks in advance

bobo122 said:
hey
long story short, i bricked my nitro hd by mistake while going back to stock (typo error in dd command) and i need some files from a working phone to attempt a last attempt to save it before i send it to Jtagging service.
there is a small program in this thread that will collect all the bootloaders i need (it needs root access)
if you're in windows you should run backup.bat from Brixfix-2-1.zip.
if you're in linux then you should run get-part.sh and getpartbin.py
thanks in advance
Click to expand...
Click to collapse
there are unbricking files posted in the unbricking threads...

KronicSkillz said:
there are unbricking files posted in the unbricking threads...
Click to expand...
Click to collapse
it doesnt have all the files i need (i mistakenly overwritten mmcblk0p2 when i was supposed to overwrite mmcblk0p27, i guess thats SBL1..
the little program in the thread i mentioned can bring me all the files i need (including SBLs and other files)
thanks for the reply though

If your phone is in unbooteable state, black screen, then you most probably need jtag. Describe the state of the phone.
Sent from my HTC One VX using xda premium

el_venga said:
If your phone is in unbooteable state, black screen, then you most probably need jtag. Describe the state of the phone.
Sent from my HTC One VX using xda premium
Click to expand...
Click to collapse
its black screen , and i was getting hsusb_qdload when connecting it to the computer (code 9008) , then i tried a chines program that flashes files to the emmc .. all i had was the su640 files (they were included in the same chines thread , p930 was mentioned there) ..
after the flash , its still black screen but now windows installs new drivers (code 9025) - check the attached photo.
as far as my understanding goes this is sd mode.. the flashing software is still able to see the cellphone, so i want to try to flash the original files this time and see what happens before i spend 80$ on jtagging

bobo122 said:
its black screen , and i was getting hsusb_qdload when connecting it to the computer (code 9008) , then i tried a chines program that flashes files to the emmc .. all i had was the su640 files (they were included in the same chines thread , p930 was mentioned there) ..
after the flash , its still black screen but now windows installs new drivers (code 9025) - check the attached photo.
as far as my understanding goes this is sd mode.. the flashing software is still able to see the cellphone, so i want to try to flash the original files this time and see what happens before i spend 80$ on jtagging
Click to expand...
Click to collapse
This is Qualcomm mode. Dunno why you got two different ids but I might give you the files in a day or two. I have a p930.
Sent from my HTC One VX using xda premium

el_venga said:
This is Qualcomm mode. Dunno why you got two different ids but I might give you the files in a day or two. I have a p930.
Sent from my HTC One VX using xda premium
Click to expand...
Click to collapse
great, thanks a lot

Mine bricked just now. Was testing a micro sdcard and afterwards just black screen and hsusb now. Did you repaired yours?
Sent from my LG-E970 using XDA Premium 4 mobile app

nope .. no luck ..

try this method
may this method works for you http://bbs.gfan.com/forum.php?mod=viewthread&tid=4520374&ordertype=1
all you need is correct files otherwise your phone will be totally dead even not jtagable

Related

[Q] Can flashing a custom ROM harm the phone's board ?!

I was trying to flash a custom ROM to my my htc DHD, changing the phone's ROM from Android Revolution HD 7.0.4 to a Miui ROM. During the process the mobile went to a complete black screen with nothing else happening, I opened the bootloader and the same thing happens when I try to boot to Recovery, but it still goes in fastboot when I connect the phone to the laptop, so I thought that I've mistakenly deleted the Recovery files from the phone, I tried to push the files using adb but it always said that the device is not found, after several tries I decided to pay a visit to htc customer service where they told me that the phone's board was harmed during the process, having bad history with htc customer service with 2 previous visits both went horribly wrong and they didn't even have the phone checked, only tried to boot it and then jumped to the conclusion, I've had to ask you people for help !!
Here is how I tried to flash the ROM to the already rooted mobile:
I some how thought about using the following method to change the recovery from EXT4 to ClockworkMOD .. I don't know what I was thinking or how high I was at that moment but it really happened using the Advanced Ace Hack Kit
Then the mobile has gone black and story I told before happened, my question now is, can this process or any software development process harm the phone's board by any means ?! and could this problem I'm facing be really with the phones board ?!
No, just head back to the hack kit forum there is a link there for IRC chat help from the guys there. You may have just corrupted your bootloader image. Those working in customer service can't tell you which end is their brain and which end is their rear
Sent from my Desire HD using xda premium
I've tried to contact them with the problem when it first happened but they refused to help me telling that I've used the kit for what it's not meant for .. they were kind of arrogant but .. they've got a point !
You will need to install the stock ATT gingerbread ROM using your PC: http://dl4.htc.com/RUU_Ace_Gingerbre...368_signed.exe You will then have to re-root using the Hack Kit.
Sent from my Desire HD using xda premium
Link ain't working, plus how would i install in via pc if the adb can't see the device loaded to the computer ?!
hmm .. i got it .. it's all solved now .. thanks a lot man
El_Marakbi said:
hmm .. i got it .. it's all solved now .. thanks a lot man
Click to expand...
Click to collapse
No problem just remember read search and learn before you try anything on your phone, we all had to do it. Also stick with ext4 for rom flashing its what we all use. I dont even bother with rom manager anymore.
Welcome to XDA and enjoy the learning.
El_Marakbi said:
hmm .. i got it .. it's all solved now .. thanks a lot man
Click to expand...
Click to collapse
How did you solve it?
Sent from my HTC Desire HD
Muikkuman said:
How did you solve it?
Sent from my HTC Desire HD
Click to expand...
Click to collapse
google the "RUU Ace Gingerbread S Cingular US 2.47.502.7 Radio 12.56.60.25 26.10.04.03 M release 200368 signed" then swich on the mobile and let load to the black screen that used to pop up to me, attach the mobile to the laptop and launch the stock ROM .. it'll do everything and leave the mobile with the stock unrooted ROM, then reroot the device with the aahk.

[Q] Unbrick QHSUSB_DLOAD

Is there any progress on unbricking the htc one v, I've tried using the unlimited.io method with no luck, any help would be appreciated
in the word's of myself, your buggered....you need to send it to Repair centre..
1st hand experience here
Haha thought as much, ah well thanks anyway
or find someone with a riffbox, if its really DLOAD mode and not diagnostic then its ready for revival and wont even need cracking open (and youll get s-off/supercid too)
What's that ??
donhashem.dh said:
What's that ??
Click to expand...
Click to collapse
its a jtag box that supports several htc phones by usb you just have to short the emmc while connecting the usb to get into qcom dload mode, if youve already got dload mode you just need to connect to the riffbox and hit ressurect (and set your cid to 11111111 if you want) it will get you back to the bootloader with s-off and you can flash an ruu from there to revive it fully
Can we purchase that from stores ??
And if its hard bricked ......will it work ??
Emba4 said:
or find someone with a riffbox, if its really DLOAD mode and not diagnostic then its ready for revival and wont even need cracking open (and youll get s-off/supercid too)
Click to expand...
Click to collapse
not always, this problem shows for 2 things
1) ALL or some of the nand is broken due to radio and needs to go to HTC
2) as you said, IF it's just in DLOAD, and we have a program in the android development forum for it..
Btw if they take it to HTC what do they fix in it ??
motherboard ^
Sent from my One V
But how is hardware related with software ,if the bootloader got corrupted then why motherboard ??
Who said BL is corrupted the partitions get corrupt if I an not wrong
Sent from my One V using xda app-developers app

Help to repair the phone stucked on Qload state

I wrote this request in another thread and I think hasn't been read by many people, so I opened a specific thread.
Our phone may remain stucked for several reasons in a QLOAD 9008 device state, or similar device (easily verifiable even with Windows). It's better to test a solution very simple and useful for all.
To do this is required to extract some files residing in an area of ​​the phone's memory and only a working phone can be used to extract a dump of this files following how explained in this thread:
http://forum.xda-developers.com/showthread.php?t=2136738
Don't think an hardbrick can't happens to you, it may happens and without a tested solution your phone may become a paperweight. Alas my phone is bricked (!), I cannot extract any file from it, I can only try to repair the phone but I need this files to test this method. I invite anyone who has care of his phone to read the topic linked above and try to extract the files needed to repair the phone locked in QDLOAD mode (05c6:9008), we have only this way to unbrick the hardbricked phone for free (if the phone warranty is expired or invalid).
I thank anyone (uhm... mr. Arco68?...) who gives a hand to solve the "Qload 9008 mode" brick problem with this method!
I hope that someone will help you.
I've read the thread, and I'm willing to help... but what exactly I have to do?
Honestly, I can't make any sense of the thread...
Sent from my GT-I8150 using xda app-developers app
yep,,,, and i thought so too,,,,,
even arco himself mentioned he had two hard bricks,,, i dont think,, he just returned it to sammy for warranty use.. i think he had that unbricker you're mentioning..
R: Help to repair the phone stucked on Qload state
santiagoruel13 said:
yep,,,, and i thought so too,,,,,
even arco himself mentioned he had two hard bricks,,, i dont think,, he just returned it to sammy for warranty use.. i think he had that unbricker you're mentioning..
Click to expand...
Click to collapse
Why don't give a try?
Inviato dal mio GT-I8150 con Tapatalk 2
Today, or as soon as possible, I'll try to make backups of the bootloader, partition table and a .pit from an i9100. If I cannot do that, as soon as possible I will try with a i9001 that has hardware very similar to the i8150. I hope I can do it, so I will explain here how to do it step by step to allow other users do the same more easily. Stay tuned!
orsonbear said:
Today, or as soon as possible, I'll try to make backups of the bootloader, partition table and a .pit from an i9100. If I cannot do that, as soon as possible I will try with a i9001 that has hardware very similar to the i8150. I hope I can do it, so I will explain here how to do it step by step to allow other users do the same more easily. Stay tuned!
Click to expand...
Click to collapse
Will a dd dump be enough?
Sent from my GT-I8150 using xda app-developers app
pepoluan said:
Will a dd dump be enough?
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
I don't think, because i think isn't compatible with the tool...

i747 Hard Bricked: QHSUSB - DLOAD : Needing a debrick.img

SGH-I747 (4.1.2 i747's please)/ SGH-i747m( If you have a official 4.3 i747m, please post a debrick.img) only:
Hi, I recently hard bricked my phone into QHSUSB DLOAD and I am going to attempt repairing it through the SD Card boot method.
http://forum.xda-developers.com/editpost.php?do=editpost&p=47431259
I need a debrick.img to flash to the SD card in a Linux OS.
I would have gotten it myself but my phone is obviously dead. I found one before on XDA, but it did not work on my device and it gave me an error in the Linux terminal when it should not have.
-snip-
The end of the 3rd boot-loader stage in mmcblk0 is at 77.3 megabytes. If you are going to help out using your device, try to refrain from uploading an image with a different ROM other than root.
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/backup.img bs=2m count=81054925
The count is the amount of bytes. I am not sure if it is meant to be 1000 bytes=kilobyte or 1024 bytes=kilobyte. The count above is for 1024.
I need someone to install the Galaxy S III unified toolkit, and pull the first 7 partitions from mmcblk0 ,which is where the third bootloader stage ends.(Don't upload a heavily modified device please) http://www.skipsoft.net/?page_id=213 Once you get the files, PM me.
If anyone has a link to a working one, please post that. If you want to get your own image to help me, go ahead.
Thanks guys.
Sorry for the bump... I just need the device running again since the state it's in, it CAN be unbricked.
99ytrewq9111 said:
Sorry for the bump... I just need the device running again since the state it's in, it CAN be unbricked.
Click to expand...
Click to collapse
what happened?
winosxbuntu said:
what happened?
Click to expand...
Click to collapse
I tried to unlock what I thought was a locked bootloader(I could only enter bootloader through ADB)
I found an article that says ezunlock works on all S III's.
It corrupted my bootloader,and my phone gives off no signs of life except "Device QHSUSB-DLOAD not recognized" when plugged in.
This means the motherboard/processor wasn't able to boot from the hard disk, so then it tries the SDcard if it matches the phone close enough.
I need someone to use their rooted i747 to dump the first 77.3 megabytes of "mmcblk0". That contains the firmware and bootloaders. With that, i can burn it to an sdcard in a linux operating system and plug it into my phone.
99ytrewq9111 said:
Sorry for the bump... I just need the device running again since the state it's in, it CAN be unbricked.
Click to expand...
Click to collapse
99ytrewq9111 said:
I tried to unlock what I thought was a locked bootloader(I could only enter bootloader through ADB)
I found an article that says ezunlock works on all S III's.
It corrupted my bootloader,and my phone gives off no signs of life except "Device QHSUSB-DLOAD not recognized" when plugged in.
This means the motherboard/processor wasn't able to boot from the hard disk, so then it tries the SDcard if it matches the phone close enough.
I need someone to use their rooted i747 to dump the first 77.3 megabytes of "mmcblk0". That contains the firmware and bootloaders. With that, i can burn it to an sdcard in a linux operating system and plug it into my phone.
Click to expand...
Click to collapse
find a download link for this http://forum.xda-developers.com/showthread.php?t=1746665 (samsung galaxy s3 toolkit) which can help you fix your phone
if that does not help take it to mobiletechvideos.com and they will fix it for you REASONABLE PRICE
its XDA you will get the help you deserve PLUS i have never encounted that kind of problem HOPE TO GOD IDONT but again am sure an SD-CARD that can write firmware/system IS VALUABLE/USEFULL compared to nothing and that means there is hope left to fix bad code :laugh:
winosxbuntu said:
find a download link for this http://forum.xda-developers.com/showthread.php?t=1746665 (samsung galaxy s3 toolkit) which can help you fix your phone
if that does not help take it to mobiletechvideos.com and they will fix it for you REASONABLE PRICE
its XDA you will get the help you deserve PLUS i have never encounted that kind of problem HOPE TO GOD IDONT but again am sure an SD-CARD that can write firmware/system IS VALUABLE/USEFULL compared to nothing and that means there is hope left to fix bad code :laugh:
Click to expand...
Click to collapse
Thanks for that link! It looks very promising, and I can probably find a stock boot.IMG in there. I will work on tomorrow. If I succeed, I'll edit the OP and make a debrick guide for this drvice forum. A word of advice, try not to mess with your bootloader or you end up like me
winosxbuntu said:
find a download link for this http://forum.xda-developers.com/showthread.php?t=1746665 (samsung galaxy s3 toolkit) which can help you fix your phone
if that does not help take it to mobiletechvideos.com and they will fix it for you REASONABLE PRICE
its XDA you will get the help you deserve PLUS i have never encounted that kind of problem HOPE TO GOD IDONT but again am sure an SD-CARD that can write firmware/system IS VALUABLE/USEFULL compared to nothing and that means there is hope left to fix bad code :laugh:
Click to expand...
Click to collapse
Hi, the toolkit didn't fix my phone, but its defiantly a step up. Since I'm assuming you have the toolkit installed that you suggested it, could you do me a favor?
It will be a bit easier using the toolkit to extract the partition files. If you could pull the first 7 partitions from "mmcblk0" of your device through the toolkit, it will probably set the next step to fix my phone. (Assuming you have a 16g i747... I don't really know)
You don't have to do this of course.
Thanks man.
Bump. Can anyone help out? All I need is the first 7 partitions.
Sent from my GT-I9300 using xda app-developers app
99ytrewq9111 said:
Bump. Can anyone help out? All I need is the first 7 partitions.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
either try using this link http://forum.xda-developers.com/showpost.php?p=27239761 am pretty sure it works for all S3 models, either way on the I747 forum it has been removed, the download link does not work........ so use this
it will work, it may not work but for the time being use this toolkit and also search forums or Google on how to fix this without, i think i found some answers after i had an emmc brick with my S2 but i did not have an SD card to re-write firmware to work again on my phone so i bought the S3 and its awesome
winosxbuntu said:
either try using this link http://forum.xda-developers.com/showpost.php?p=27239761 am pretty sure it works for all S3 models, either way on the I747 forum it has been removed, the download link does not work........ so use this
it will work, it may not work but for the time being use this toolkit and also search forums or Google on how to fix this without, i think i found some answers after i had an emmc brick with my S2 but i did not have an SD card to re-write firmware to work again on my phone so i bought the S3 and its awesome
Click to expand...
Click to collapse
The problem is I need a working phone to pull the partitions. :/ I tried to use the boot image, but it had an error writing while in the linux.
99ytrewq9111 said:
The problem is I need a working phone to pull the partitions. :/ I tried to use the boot image, but it had an error writing while in the linux.
Click to expand...
Click to collapse
This one worked for me http://forum.xda-developers.com/showpost.php?p=46258374&postcount=172
I have a similar problem Hard Bricked after update to 4.3 tried to flash my phone Backup 4.1.2 and died can not log in or recovery nor danlold.Is there any solution.
Bradkirk said:
This one worked for me http://forum.xda-developers.com/showpost.php?p=46258374&postcount=172
Click to expand...
Click to collapse
Did you use an i747 or a i747m device?
If a i747m image works on an i747, it will basically fix all of my problems.
spensa said:
I have a similar problem Hard Bricked after update to 4.3 tried to flash my phone Backup 4.1.2 and died can not log in or recovery nor danlold.Is there any solution.
Click to expand...
Click to collapse
What message appears on your computer when you plug it in?
If it says QHSUSB-DLOAD, you are in faint light.
It stands for Qualcomm High Speed USD Download Mode.
What is means that your processor(qualcomm), is trying to boot, but it cannot find proper drivers for the hardware.
It will then look for something to boot from in the SDcard.
Here is a thread on how some other people were able to do it : http://forum.xda-developers.com/showthread.php?t=2439367
I have an I747M technically. I went for an actual I747M image just in case there was a slight difference. in the thread that one came from though there should be one for the actual att device if you look through it.
and just to confirm, yes the phone was blank and unresponsive. showing up as QHSUSB-DLOAD before i loaded that img onto my external SDcard. and I am using the same phone currently.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Bradkirk said:
I have an I747M technically. I went for an actual I747M image just in case there was a slight difference. in the thread that one came from though there should be one for the actual att device if you look through it.
and just to confirm, yes the phone was blank and unresponsive. showing up as QHSUSB-DLOAD before i loaded that img onto my external SDcard. and I am using the same phone currently.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Unfortunately that's the download I found that didn't work.
Thanks for trying though
damn! the only other help I can offer then, is that there is a pretty good thread on this over in the d2tmo section. someone there wrote a little tool to easily download the relevant data. might help you on your quest. or at least make it so you could ask someone that doesnt know ADB. best of luck!
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
99ytrewq9111 said:
What message appears on your computer when you plug it in?
If it says QHSUSB-DLOAD, you are in faint light.
It stands for Qualcomm High Speed USD Download Mode.
What is means that your processor(qualcomm), is trying to boot, but it cannot find proper drivers for the hardware.
It will then look for something to boot from in the SDcard.
Here is a thread on how some other people were able to do it : http://forum.xda-developers.com/showthread.php?t=2439367
Click to expand...
Click to collapse
when connected to the computer written QHSUSB-DLOAD,
spensa said:
when connected to the computer written QHSUSB-DLOAD,
Click to expand...
Click to collapse
OK , take out your battery and tell me your model number(Behind battery). And what phone company do you use?
Did you possibly save a NANDROID on a computer?
( if you have i747m, you can fix your phone, but its hard to do( I havnt done it yet)
Download this image http://forum.xda-developers.com/showpost.php?p=46258374&postcount=172 (thanks to @Bradkirk )
Follow these directions using that image above^^^ http://forum.xda-developers.com/showthread.php?t=2439367
You need to install a Linux operating system (Ubuntu works) to run the commands.
Edit:! According to the T-Mobile thread, you might need a debrick.IMG from a phone on 4.3
Once I know your phones model number, I can edit the main post and ask for you phone model's images.
99ytrewq9111 said:
OK , take out your battery and tell me your model number(Behind battery). And what phone company do you use?
Did you possibly save a NANDROID on a computer?
( if you have i747m, you can fix your phone, but its hard to do( I havnt done it yet)
Download this image http://forum.xda-developers.com/showpost.php?p=46258374&postcount=172 (thanks to @Bradkirk )
Follow these directions using that image above^^^ http://forum.xda-developers.com/showthread.php?t=2439367
You need to install a Linux operating system (Ubuntu works) to run the commands.
Edit:! According to the T-Mobile thread, you might need a debrick.IMG from a phone on 4.3
Once I know your phones model number, I can edit the main post and ask for you phone model's images.
Click to expand...
Click to collapse
I took it to a service to repair

bricked m8

i flashed lg kernel on my m8 by wrong now the phone dosent turn on
or reboot via volume + power
and the pc recognize it as "QHSUSB_BULK"
ANY HELP
U have probably turned ur m8 into a paperweight ? only thing to do now is keep pressing power button and volume. Try through pc cmd - adb reboot-bootloader just to see . Sucks mate hopefully it works out for you
LG kernel.....seriously !!!
Mr Hofs said:
LG kernel.....seriously !!!
Click to expand...
Click to collapse
was mistake
any help ?
Mr Hofs said:
LG kernel.....seriously !!!
Click to expand...
Click to collapse
error |: device not found
As soulja already said. Boot the phone to the bootloader and recovery. Reflash a rom. If that is impossible to achieve there is absolutely nothing we can do.
Mr Hofs said:
As soulja already said. Boot the phone to the bootloader and recovery. Reflash a rom. If that is impossible to achieve there is absolutely nothing we can do.
Click to expand...
Click to collapse
it wont boot or respond even for charger
Then it's proper dead.....
Good try the Adb command Adb reboot bootloader see if you can get into that but might be tricky
Edit.... Just seen your last post hope you have insurance
Won't something like this work on that device, of course downloading the correct HTC One M8 equivalent files?
qhsusb_bulk detection lg g2 fix
what dongle i need for it ?
But if the device is not even switching on its a no go right ?
Mr Hofs said:
But if the device is not even switching on its a no go right ?
Click to expand...
Click to collapse
Yeah.
I can recall also reading something some time ago about making your SD Card(External) the bootable one and then fixing the "internal" from there but I'm not sure if that will even work either, was for another device as well.
I don't think a lot of developers/"hackers" on here sat down trying to figure out solutions to a problem that isn't so frequent on this device. I mean, who would flash a LG "anything" on an HTC...
Just wondered if it might work out seeing as it at least "detects" that much from the phone. It's a type of Qualcomm recovery mode isn't it, QHUSB-etc etc
Figured that maybe it is in a "semi" on condition already, it's just that you can't do anything with it. But if it's completely broke then might as well take it into service center for repair. Don't know what you're gonna tell them though @escoda
Yep. From what i know on the htc one x, once you turn off the phone completely (no hibernation mode) and you plug it in the pc it goes automatically to a adb hibernation mode. That's why its in the device manager. So it reads the device but can't respond correctly. But to get a step ahead it's very necessary to turn the device on.
@escoda its not completely bricked yet. Just go to ubuntu and follow the guide mentioned from Brendm14. Like he also said you only need to download then those files for the htc one m8. Most qualcomm devices have everything on the same partition but you could probably examine or the bootloader and the other required stuff are the same partition number as in the guide. If so then you still just need to download the htc files and do it the same.
I dont know where you can get the htc files since I am/was an LG user.
wulsic said:
@escoda its not completely bricked yet. Just go to ubuntu and follow the guide mentioned from Brendm14. Like he also said you only need to download then those files for the htc one m8. Most qualcomm devices have everything on the same partition but you could probably examine or the bootloader and the other required stuff are the same partition number as in the guide. If so then you still just need to download the htc files and do it the same.
I dont know where you can get the htc files since I am/was an LG user.
Click to expand...
Click to collapse
Those files are present on any firmware.zip for the appropriate phone model.
Flashing just a wrong kernel would not do that. Something must have happened that messed with the bootloader.
r3pwn said:
Flashing just a wrong kernel would not do that. Something must have happened that messed with the bootloader.
Click to expand...
Click to collapse
what can i do ??
its out of warranty
escoda said:
what can i do ??
its out of warranty
Click to expand...
Click to collapse
If you have an extra SDcard laying around, I would be happy to help you try to get your phone working (see posts above).
r3pwn said:
If you have an extra SDcard laying around, I would be happy to help you try to get your phone working (see posts above).
Click to expand...
Click to collapse
yes i have SDcard ...
i tried Ubuntu and when i write (ls /dev/sd*) it return with /dev/sda /dev/sda1 /dev/sda2 /dev/sda5

Categories

Resources