Related
My phone is unlocked and rooted. My problem is that when I go to FASTBOOT MODE, then go into RECOVERY, then when I press 'apply update from /sdcard' it shows nothing in there. So, I just stuck and unable to flash any rom at all. I tried to go into the SD card through my computer to install a ROM so that I have something to flash, but nexus s has only internal storage. Please help?
Hi
Hi, I bought my nexus s, immediately after I tried to root, and failed, this left me in the same situation as you.
You NEED to install the adb drivers, and boot using odin files. It was pretty tricky but i got there in the end, i was bricking it too , but dont worry, there's a 98% chance its not bricked, ill find the files for you now...
Go to mount drives and mount your storage from there. That's what I did.
Right, first of all, boot into the bootloader on your Nexus S, and i'm assuming that all your drivers are working fine because you have already unlocked your bootloader.
Place the files in the zip download inthe following places
WIN32bitOS: Program files/Android/Android-sdk/tools
WIN64bitOS: Program files (x86)/Android/Android-sdk/tools
Next, open a command prompt, and type in the following commands, (C: is your windows installation hard drive letter, leave as default if you dont know what this means)
if your 32bit type this w/o quotes "cd C:/Program files/Android/Android-sdk/tools
64bit "cd C:/Program files (x86)/Android/Android-sdk/tools
and click enter.
Next you want to make sure that your Nexus S is in bootloader mode, connected to your pc.
Type the following.
fastboot flash boot boot.img
[click enter & wait until it says successful]
fastboot flash recovery recovery.img
[click enter & wait until it says successful]
fastboot flash system system.img
[click enter & wait until it says successful]
fastboot flash userdata userdata.img
[click enter & wait until it says successful]
Reboot and you should go into android 2.3
Next time make a nandroid backup in clockwork mod!
Download link : http://www.megaupload.com/?d=GI9P4F5I
cdaly985 said:
Right, first of all, boot into the bootloader on your Nexus S, and i'm assuming that all your drivers are working fine because you have already unlocked your bootloader.
Place the files in the zip download inthe following places
WIN32bitOS: Program files/Android/Android-sdk/tools
WIN64bitOS: Program files (x86)/Android/Android-sdk/tools
Next, open a command prompt, and type in the following commands, (C: is your windows installation hard drive letter, leave as default if you dont know what this means)
if your 32bit type this w/o quotes "cd C:/Program files/Android/Android-sdk/tools
64bit "cd C:/Program files (x86)/Android/Android-sdk/tools
and click enter.
Next you want to make sure that your Nexus S is in bootloader mode, connected to your pc.
Type the following.
fastboot flash boot boot.img
[click enter & wait until it says successful]
fastboot flash recovery recovery.img
[click enter & wait until it says successful]
fastboot flash system system.img
[click enter & wait until it says successful]
fastboot flash userdata userdata.img
[click enter & wait until it says successful]
Reboot and you should go into android 2.3
Next time make a nandroid backup in clockwork mod!
Download link coming in 9 mins... data uploading
Click to expand...
Click to collapse
hi cdaly, can you point me to some information on how to install nandriod backup and making/restore a backup right after installing CWM (right after "unlocked" but didnt install Super user yet)?
Yeah
Yeah sure,
Root your phone, go to market place, download rom manager. Open the app and click the button that says, Fash Clockwork Recovery.
Shut down your phone when the operation has completed. Go inot bootloader mode, click recovery. Navigate to backup and restore. Go into backup and restore, click backup. Voila.
If you ever need to restore do the same but click restore. Pretty simple when you know what to do
If this has left you confused, look around on XDA/google, there are a ton of guides
Link added!
Thanks, appreciate it.
Thanks for that. I am using mac computer. Would it be the same typing command for mac as you had mentioned?
cdaly985 said:
Yeah sure,
Root your phone, go to market place, download rom manager. Open the app and click the button that says, Fash Clockwork Recovery.
Shut down your phone when the operation has completed. Go inot bootloader mode, click recovery. Navigate to backup and restore. Go into backup and restore, click backup. Voila.
If you ever need to restore do the same but click restore. Pretty simple when you know what to do
If this has left you confused, look around on XDA/google, there are a ton of guides
Link added!
Click to expand...
Click to collapse
Thanks very much cdaly.. I am just a bit confused regarding phone is rooted or not.
I got to the point flash recovery was sucessfuly in command prompt, but when i try to install "su-2.3.6.1-cd-signed.zip" from SD card, it wasn't successful, as in there is no "superuser" icon after reboot and i have tried wifi tether and it says my phone is not root.
Now i havent tried "su-2.3.6.1-ef-signed.zip" because i accidently bricked my phone for some stupid things i did. but my phone is NOT root as long as I don't see the superuser program right?
I thought nandroid is an actual program but it just means backing up through bootloader?
Thanks for all your help!!!
Thanks very much cdaly.. I am just a bit confused regarding phone is rooted or not.
I got to the point flash recovery was sucessfuly in command prompt, but when i try to install "su-2.3.6.1-cd-signed.zip" from SD card, it wasn't successful, as in there is no "superuser" icon after reboot and i have tried wifi tether and it says my phone is not root.
Now i havent tried "su-2.3.6.1-ef-signed.zip" because i accidently bricked my phone for some stupid things i did. but my phone is NOT root as long as I don't see the superuser program right?
I thought nandroid is an actual program but it just means backing up through bootloader?
Thanks for all your help!!!
Click to expand...
Click to collapse
I dont know if NANDROID is a program or not, it just use it via clockwork mod recovery menu and it works so I'm not complaining aha
If you want to root your nexus s, download this zip file and extract, make sure that your nexus s is in bootloader mode and double click "install-superboot-windows" Bingo, you have root.
Thanks for that. I am using mac computer. Would it be the same typing command for mac as you had mentioned?
Click to expand...
Click to collapse
It wouldn't hurt to try but I dont think so. If you can go into boot-camp or use a friends PC. Or you can try this.
Change your folder to the plaform-tools folder. I dont know how to do this, just referencing off of http://rootzwiki.com/wiki/index.php/Samsung_Nexus_S
Next type
"./fastboot flash boot boot.img"
"./fastboot flash recovery recovery.img"
"./fastboot flash system system.img"
"./fastboot flash userdata userdata.img"
Hi cdaly985
I'd tried it and it works 100%. And, just to share for mac to add on the command "./fastboot-mac ....". I am really impressed with your help. Thanks very very very much.
Hi cdaly985
Now everything is ok with the phone except that it won't be able to go into recovery mode. I had tried by using Rom manager v.4.. and also by pressing vol + power, all failed.
Please help me on this problem. Thanks.
I wiped the system thinking it was part of the system factory reset in TWRP but i didnt know that it would result in it saying NO OS INSTALLED. i read other similar threads about this problem but dont exactly understand what to do and how to restore my phone. i have a nandroid backup but its on my pc and not the internal storage on the phone. im fairly new to this so those replying, please explain exactly what to do. Im so scared about what to do now :crying::crying::crying:
Don't be scared its common and very, very easy to fix
Now I don't use TWRP so I have no idea of the directory structure so I can't advise you exactly.
But what you will essentially do is use adb push to get the files on your phone.
Click the link in my signature to go to the sticky roll up thread. All the important threads are linked there. Y
In that thread you'll quickly find my adb info thread. This should be most of what you need to know
Sent from my Nexus 5 using Tapatalk
First relax, your phone is not ruined. I assume you have a custom recovery. You're going to have to either side load a rom zip using adb or adb push a rom zip onto your phone and flash it in recovery.
Edit, OP you'll want to push the rom to /sdcard/Download. That'll put it into the folder twrp defaults to look for it.
Sent from my Nexus 5 using XDA Free mobile app
Well, you have three pretty easy options.
TWRP supports ADB commands, but the stock Google driver won't work. If you install the Universal ADB Driver you should be able to push your backup to your device (adb push [file location on your computer] [where to push on your phone])
http://www.koushikdutta.com/post/universal-adb-driver
You could also flash a ROM through adb sideload. Download a ROM zip to your computer, then in TWRP choose Advanced -> ADB Sideload. Then run "adb sideload [zip file]" to sideload the ROM you downloaded.
Last, you can restore to the Nexus Factory Image.
https://developers.google.com/android/nexus/images
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
raptir said:
]
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
Click to expand...
Click to collapse
Luckily its easier install adb and fastboot than the ask method. Just go to the thread mentioned earlier and use the 15 second installer
OP, no matter what you'll need run that installer
Sent from my Nexus 5 using Tapatalk
All these guys have it spot on! I just wanted to mention that when you install a ROM system gets wiped automatically as this is a parameter in the zip's updater-script.
So in other words there is really no reason to wipe system manually. Just let the install process do it for you. If u wipe system manually and then you realize you do not have a ROM zip or a nandroid only ADB can save you. So this way you can save yourself a headache
raptir said:
Well, you have three pretty easy options.
TWRP supports ADB commands, but the stock Google driver won't work. If you install the Universal ADB Driver you should be able to push your backup to your device (adb push [file location on your computer] [where to push on your phone])
\
You could also flash a ROM through adb sideload. Download a ROM zip to your computer, then in TWRP choose Advanced -> ADB Sideload. Then run "adb sideload [zip file]" to sideload the ROM you downloaded.
Last, you can restore to the Nexus Factory Image.
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
Click to expand...
Click to collapse
I downloaded everything and ran the flash-all . bat file but its currently been on < waiting for device > for a while now. i think it didnt detect the phone although it is connected through the USB :/
thauri said:
I downloaded everything and ran the flash-all . bat file but its currently been on < waiting for device > for a while now. i think it didnt detect the phone although it is connected through the USB :/
Click to expand...
Click to collapse
Did you or did you not read my adb and fastboot thread?
And WHY are you going for the last resort first???
You really need to chill out and read things because I don't think you're thinking straight
Sent from my Nexus 5 using Tapatalk
raptir said:
Well, you have three pretty easy options.
TWRP supports ADB commands, but the stock Google driver won't work. If you install the Universal ADB Driver you should be able to push your backup to your device (adb push [file location on your computer] [where to push on your phone])
You could also flash a ROM through adb sideload. Download a ROM zip to your computer, then in TWRP choose Advanced -> ADB Sideload. Then run "adb sideload [zip file]" to sideload the ROM you downloaded.
Last, you can restore to the Nexus Factory Image.
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
Click to expand...
Click to collapse
rootSU said:
Luckily its easier install adb and fastboot than the ask method. Just go to the thread mentioned earlier and use the 15 second installer
OP, no matter what you'll need run that installer
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
yeah i did download the 15 second ADB installer but my computer isnt detecting the phone connected when i ran the flash-all . bat file.
1) you need to read the whole of my thread. There are drivers to install
2) Still dont understand why you're running flashall bat when you can just adb push your backup to your sdcard. You know you lose all your data when you do that?
Sent from my Nexus 5 using Tapatalk
rootSU said:
1) you need to read the whole of my thread. There are drivers to install
2) Still dont understand why you're running flashall bat when you can just adb push your backup to your sdcard. You know you lose all your data when you do that?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
ok yes im reading your thread and doing the ADB commands. i have a question though, the multi-line input for the code to ADB push goes in cmd right? how is that possible?
Yes
Type one line, press enter, type another line, press enter
Sent from my Nexus 5 using Tapatalk
rootSU said:
Yes
Type one line, press enter, type another line, press enter
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
when i press enter after adb shell and mount data, it says data failed : Device or Resource busy
thauri said:
when i press enter after adb shell and mount data, it says data failed : Device or Resource busy
Click to expand...
Click to collapse
If "mount data" shows device or resource busy, then that usually means it is already mounted.
rootSU said:
If "mount data" shows device or resource busy, then that usually means it is already mounted.
Click to expand...
Click to collapse
i did everything but in the last part, it doesnt transfer the recovery files to the phone
Edit: The files are transferring successfully but only one at a time.
EDIT 2: All the necessary files were transferred but the TWRP recovery mode isnt detecting it as a restore option
Messing up is scary but it's a great opportunity to learn. I think you'll get through this just fine.
thauri said:
i did everything but in the last part, it doesnt transfer the recovery files to the phone
Edit: The files are transferring successfully but only one at a time.
EDIT 2: All the necessary files were transferred but the TWRP recovery mode isnt detecting it as a restore option
Click to expand...
Click to collapse
It must be in the exact location twrp needs to see it.
Sent from my Nexus 5 using Tapatalk
rootSU said:
It must be in the exact location twrp needs to see it.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I did, I put it in the backup folder in TWRP where all the other backups usually were
thauri said:
I did, I put it in the backup folder in TWRP where all the other backups usually were
Click to expand...
Click to collapse
Take a new backup, then delete everything in the new backup folder and move everything from your old backop into the new backup folder,
So for example
Code:
adb shell
mount /data
cd /data/media/0/TWRP/backups
ls
^^ This should list the contents... You should see your old backup and your new backup (which will be mostly empty).
Lets pretend your new backup folder is 22222222 and your old backup folder is 11111111
Code:
rm -Rf 222222222/*
mv 111111111/* 222222222
The first command is a remove (recursive) of the contents of the new backup. second command mvs contents of old backup into new backup folder,
Try that.
I don't know TWRP so my assumptions of the path may be incorrect
Someone else posted twrp default path as /sdcard/downloads - try that.
Hi, my G6-U10 is hard bricked and has gone to QDLoader 9008 mode so i cant go to recovery, fastboot,adb mode .
i need EMMC image of a similare device (G6-U10) so i can fix it following instructions in this thread .
i dont need whole EMMC image, just first 100-200 MB .
to extract EMMC, you need to be on stock rom with root access.
to do so:
1. Enable "USB debugging" in "Developer Options". then connect your device to Windows PC.
2. download and extract ADB. then run the following command through CMD:
Code:
adb shell
su
dd if=/dev/block/mmcblk0 of=/sdcard/EMMC.img bs=100m count=1
note that you must enter each row separately and confirm the dialogs appeared on your device screen to grant root and adb access for pc. the option bs=100m mean that the dd command will only extract first 100MB of EMMC. and FYI, this file is only backup from system partition, not from any private files, no need to worry.
the extracted file will be in internal SD, named EMMC.img , compress it in ZIP or RAR so it will have much less size, then send it here to solve many people's problems. anybody does that, i'll appreciate.
Thanks for reading.
Credits and references:
@majdinj http://forum.xda-developers.com/showthread.php?t=2450045
@Jimmyz0r http://forum.xda-developers.com/yureka/help/guide-unbrick-hard-bricked-yureka-t3303112
@tirta.agung http://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
http://linoxide.com/linux-command/linux-dd-command-create-1gb-file/
http://unix.stackexchange.com/questions/134299/dd-bs-count-seek
https://yadi.sk/d/wtaBNFaUraZyg
washichi said:
https://yadi.sk/d/wtaBNFaUraZyg
Click to expand...
Click to collapse
Thanks bro, but it's just 100bytes, not 100Mbytes. i think you used bs=100 instead of bs=100m
please consider reuploading , you are my saviour
info on the progress:
I got EMMC image thanks to @washichi :good: (download it from attachments).
then i could finally wake my device up, in the fastboot and recovery, following instructions in this thread(first post).
i can go into Fastboot mode but though i had unlocked bootloader (before), but i can only flash recovery, system(partly) and boot partitions. other partitions give me error ((Remote: Not Allowed)).
the only recovery that i could go into, was the latest TWRP 3 . in recovery i can even connect my device in MTP mode to pc and see files on the internal SD! but i was not successful with flashing roms, it always gives me error mounting cache, system, data. ADB mode is also accessible, used adb sideload to flash rom, but it didnt worked too!
i think part of internal SD is damaged and need to be fixed somehow. still havent found out how.
so, for guys who are having problems similar to me or "Internal Storage Damaged blah blah" i recommend trying to follow these steps to see if their internal SD is still flashable or not:
1. Download an official Rom for your device and unpack it using HuaweiUpdateExtractor.
2. download and extract latest (at least 1.0.32) fastboot in the same folder as extracted huawei IMG files are (Gush bless me! there's too much grammatical erros in my texts )
3. connect your device in fastboot mode (instructions above).
4. go to the directory where all extracted files place. Hold shift and right click on empty space, chose "Open command window here".
Note: you must have an unlocked bootloader to be able to continue, type this command to see if its unlocked:
Code:
fastboot oem get-bootinfo
if you're unlocked, then continue reading, if not, i dont think there is a way to find unlock key for your device.even DC unlocker cant recognize your device in fastboot and adb.
5. now that you know you have an unlocked BL, type these commands one bye one:
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash aboot aboot.img
fastboot flash tz tz.img
fastboot flash userdata userdata.img
fastboot flash [COLOR="RoyalBlue"]XXX [/COLOR][COLOR="SeaGreen"]XXX[/COLOR].img
as i said before, i could only flash 3 partitions with success. but if you where able to flash all parts with success, your extremely have a chance to revive your device. at last, type fastboot reboot to see if you boot up successfully, if not, you will go again in fastboot mode or recovery mode.
for me, default recovery mode just freezes, so i flashed TWRP 3 instead of default recovery. you can try that too.
one more thing: you might not be successful to reboot into recovery, you must restart until you succeed. if you stuck in freezed recovery, open the device back, unscrew the little steel plate (it has 2 screws) and dettach the battery cord, wait 3 secs, re-attach it. i have done it more than 300 times now i dont even know where is the steel plate
FYI, EMMC image in the attachment is for G6-U10 only and probably will not work for other G6 models. if you want G6-L11 emmc, i can share it for you.
if anything was not clear for you, ask me.
@bugggmenot Everytime i insert the sd card and try to enter fastboot mode by holding the Volume+, the PC keeps beeping and refreshing the device manager, tho i can't see any hardware detected. The phone isn't recognizable as fastboot device and the LED is lighting in a blue color.
Any ideas?
Sashko98 said:
@bugggmenot Everytime i insert the sd card and try to enter fastboot mode by holding the Volume+, the PC keeps beeping and refreshing the device manager, tho i can't see any hardware detected. The phone isn't recognizable as fastboot device and the LED is lighting in a blue color.
Any ideas?
Click to expand...
Click to collapse
Do as follows:
1. detach the battery and retach it again.
2. connect the device to pc WITHOUT holding any buttons.
3. if you go into fastboot mode, you will see a blue "Fastboot mode" in middle of texts (and Blue LED).
4. type in cmd: fastboot devices
if your device is listed, you are good to go for flashing procedure.
oh and one more important thing: install fastboot and adb drivers. it's a global driver not device specific, so install any you van find ( sorry I can't Google it for you right now).
bugggmenot said:
Do as follows:
1. detach the battery and retach it again.
2. connect the device to pc WITHOUT holding any buttons.
3. if you go into fastboot mode, you will see a blue "Fastboot mode" in middle of texts (and Blue LED).
4. type in cmd: fastboot devices
if your device is listed, you are good to go for flashing procedure.
oh and one more important thing: install fastboot and adb drivers. it's a global driver not device specific, so install any you van find ( sorry I can't Google it for you right now).
Click to expand...
Click to collapse
Did everything still doesn't want to boot in fastboot mode.
Edit: I made it to the fastboot, thank you very much.
Sashko98 said:
Did everything still doesn't want to boot in fastboot mode.
Edit: I made it to the fastboot, thank you very much.
Click to expand...
Click to collapse
Happy to hear that. would be great if you share your way of success and your current progress on reviving the device. it might help many people.
bugggmenot said:
Happy to hear that. would be great if you share your way of success and your current progress on reviving the device. it might help many people.
Click to expand...
Click to collapse
I got it to the progress you did. Was able to flash only boot.img recovery.img and like 950MB of system.img. Yet smth makes me to think that everything i do flash is being flashed in the SDcard memory not in the internal one, is it supposed to be like that?
Edit1: Tried to flash an update.zip which i made by using huawei tools extractor from the stock recovery but the verification aborted the update. Tried with CWM by using adb sideload but there was some error while sending, also tried with TWRP which seems to erase its memory everytime when i restart the phone, the adb sideload doesnt work and couldn't found the flashable zip after i pushed it in by using adb
Sashko98 said:
I got it to the progress you did. Was able to flash only boot.img recovery.img and like 950MB of system.img. Yet smth makes me to think that everything i do flash is being flashed in the SDcard memory not in the internal one, is it supposed to be like that?
Click to expand...
Click to collapse
i dont think so.
i thought like you, but to test it i went to TWRP recovery and removed SD card, Formated SD (via MiniTool Partition) and reinserted SD into device. at this level , device cant recognize SD anymore, so i reformatted SD via TWRP (i dont remember the exact path, sorry), and this time SD appeared in PC ! so i simply put flashable SlimStock and flashed it via TWRP. but it exactly took the time that it had taken before when i tried to flash SlimStock via Sideload. and in both ways, it takes about 30 min to pass the system.img flashing ! so this can be a proof that in the both ways, images are being flashed on the internal SD, not ExSD.
any way, at this point it seems that we cannot go any further. but who knows? we made a dead device into TWRP, so why not...
bugggmenot said:
i dont think so.
i thought like you, but to test it i went to TWRP recovery and removed SD card, Formated SD (via MiniTool Partition) and reinserted SD into device. at this level , device cant recognize SD anymore, so i reformatted SD via TWRP (i dont remember the exact path, sorry), and this time SD appeared in PC ! so i simply put flashable SlimStock and flashed it via TWRP. but it exactly took the time that it had taken before when i tried to flash SlimStock via Sideload. and in both ways, it takes about 30 min to pass the system.img flashing ! so this can be a proof that in the both ways, images are being flashed on the internal SD, not ExSD.
any way, at this point it seems that we cannot go any further. but who knows? we made a dead device into TWRP, so why not...
Click to expand...
Click to collapse
Well i did try flashing img files via TWRP but it allows me to modify just recovery or boot partition. Tried also making flashable zip of the partition to run it from CWM but i get stuck.
I also tried
Code:
fastboot flashing unlock_critical
and
Code:
flashing unlock
but i recieve 3 dots, maybe i should be more patient next time to see what will happen.
===========================================================================
@bugggmenot i've found the file for G6-C00 for qualcomm bootloader platform. Will they work on G6-U10???
Sashko98 said:
Well i did try flashing img files via TWRP but it allows me to modify just recovery or boot partition. Tried also making flashable zip of the partition to run it from CWM but i get stuck.
I also tried
Code:
fastboot flashing unlock_critical
and
Code:
flashing unlock
but i recieve 3 dots, maybe i should be more patient next time to see what will happen.
===========================================================================
@bugggmenot i've found the file for G6-C00 for qualcomm bootloader platform. Will they work on G6-U10???
Click to expand...
Click to collapse
Greate! i dont know if they are similar or not but who cares, i'll give it a shot! please share files here i'll try and report back.
bugggmenot said:
i dont think so.
i thought like you, but to test it i went to TWRP recovery and removed SD card, Formated SD (via MiniTool Partition) and reinserted SD into device. at this level , device cant recognize SD anymore, so i reformatted SD via TWRP (i dont remember the exact path, sorry), and this time SD appeared in PC ! so i simply put flashable SlimStock and flashed it via TWRP. but it exactly took the time that it had taken before when i tried to flash SlimStock via Sideload. and in both ways, it takes about 30 min to pass the system.img flashing ! so this can be a proof that in the both ways, images are being flashed on the internal SD, not ExSD.
any way, at this point it seems that we cannot go any further. but who knows? we made a dead device into TWRP, so why not...
Click to expand...
Click to collapse
Why not try to repartition your device?
You can you the parted binary (google will find it) and put it on your /sdcard or / (the root folder). NOT your internald memory or any other partition thats your EMMC.
Now umount ALL partitions in recovery, except for the external sdcard. Go to the commandline in the recovery and cd to the parted binary. Now typ 'parted /dev/block/mmcblk0'.
Type 'print' to see your partition table.
You can now modify your partition table (only ext2 and fat32 partitions support, BUT you can format it whit your recovery soo it will be ext4. (Dont check RM format in settings!).
Hope this will fix the flashing problem.
Hard Brick
Hello guys, i don't know if this is the right place, but do you know how to unbrick Huawei Y550 - L03 from hard brick? My pc recognizes it in the device manager just as Android adapter PCUI (COM10) but the device itself doesn't show.
Thank you in advance if you can help me please. :crying:
Here i put EMMC for G6-L11 for people who need it:
Hello, can you explain how you made it from dead phone QDLoader 9008 to recovery?
bugggmenot said:
Here i put EMMC for G6-L11 for people who need it:
Click to expand...
Click to collapse
We should use the Yureka tutorial with this file to bring the G6-L11 to life right?
henrucci said:
We should use the Yureka tutorial with this file to bring the G6-L11 to life right?
Click to expand...
Click to collapse
only if your phone is G6-L11, then the answer is yes.
Win32disk killed for good all sdcards with g6-l11 image
Hi i'm new here and i'm really hoping someone can help me
I am using a one plus one. Running: Cyanogen OS Version 13.1.2-ZNH2KAS3P0-bacon
When I make phone calls the other person on the other end can only here static or can't even hear me at all!!! It's so frustrating not being able to talk to people. I looked on google and people are saying to disable google voice assistant which I did but I still have the same issue.
I am VERY NEW to all this rooting and stuff. I went google and youtube and people are suggesting to root the phone. I spent 5 hours watching youtube videos trying to figure out how to root my phone and put a OS on it. Every video I watch results in errors on my computer or phone.
I don't know what to do...is there a noob friendly guide? I read online that the Lineage OS is the best OS for oneplus one?
root with kingroot and done
go here for solution
https://forum.xda-developers.com/oneplus-one/development/fix-low-mic-call-t3055661
hit thumbs up for say thanks
go here for everything
https://forum.xda-developers.com/on...ex-oneplus-one-resources-compilation-t2843675
:good:
rony raj said:
root with kingroot and done
go here for solution
https://forum.xda-developers.com/oneplus-one/development/fix-low-mic-call-t3055661
hit thumbs up for say thanks
go here for everything
https://forum.xda-developers.com/on...ex-oneplus-one-resources-compilation-t2843675
:good:
Click to expand...
Click to collapse
I wouldn't share that fix too much the script is faulty and soft bricked some phones in the past.
I would rather do the fix manually.
There isn't much to do you have to change just 2 values in 2 different files.
/system/build.prop
Find
Code:
ro.qc.sdk.audio.fluencetype
Change "fluence" to "none"
/system/etc/audio_platform_info.XML
Find
Code:
SND_DEVICE_IN_HANDSET_MIC
And change the value from 40 to 4
I do this every time I flash a CM based ROM
rony raj said:
root with kingroot and done
go here for solution
https://forum.xda-developers.com/oneplus-one/development/fix-low-mic-call-t3055661
hit thumbs up for say thanks
go here for everything
https://forum.xda-developers.com/on...ex-oneplus-one-resources-compilation-t2843675
:good:
Click to expand...
Click to collapse
I did try Kingroot before and it was not even compatible with my device!
seanwlk said:
I wouldn't share that fix too much the script is faulty and soft bricked some phones in the past.
I would rather do the fix manually.
There isn't much to do you have to change just 2 values in 2 different files.
/system/build.prop
Find
Code:
ro.qc.sdk.audio.fluencetype
Change "fluence" to "none"
/system/etc/audio_platform_info.XML
Find
Code:
SND_DEVICE_IN_HANDSET_MIC
And change the value from 40 to 4
I do this every time I flash a CM based ROM
Click to expand...
Click to collapse
Am I able to make these changes without a rooted phone?
theaccountant87 said:
I did try Kingroot before and it was not even compatible with my device!
Am I able to make these changes without a rooted phone?
Click to expand...
Click to collapse
No, the directories are reachable only with root.
If your bootloader is unlocked you can just flash twrp as custom recovery through fastboot and then flash the superSU zip from the twrp recovery.
The OPO is one of the easiest phones to root ?
Haha not for me. Picture your grandma calling you to help her turn on the computer. I'm one step above that LOL.
I'm reading through the forums and there are all these confusing terms
seanwlk said:
No, the directories are reachable only with root.
If your bootloader is unlocked you can just flash twrp as custom recovery through fastboot and then flash the superSU zip from the twrp recovery.
The OPO is one of the easiest phones to root
Click to expand...
Click to collapse
theaccountant87 said:
Haha not for me. Picture your grandma calling you to help her turn on the computer. I'm one step above that LOL.
I'm reading through the forums and there are all these confusing terms
Click to expand...
Click to collapse
Here's a small guide that recaps the method I've used over the years.
*Warning* You will need to unlock your bootloader, which will factory reset your phone
1- Download and install fastboot and USB drivers https://drive.google.com/file/d/0B9fZIF6vzIBzT2ZtZkNSVFI5ZHc/view?usp=drivesdk
This is a all-in-one installer I found a long while ago and I keep it in my drive to have it always available wherever I go. Say yes to all the prompts. And reboot the PC just in case.
2- Download Twrp and SuperSU
https://eu.dl.twrp.me/bacon/twrp-3.1.0-0-bacon.img.html
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
3- Backup all your data
4- Reboot your phone into bootloader and connect it to the PC.
5- Open a command prompt where you downloaded the twrp img file and type:
Code:
fastboot oem unlock
6- Now:
Code:
fastboot flash recovery twrp-3.1.0-0-bacon.img
(same name as the downloaded file)
7- Let the phone do the first boot.
8- Reboot into recovery flash the superSU zip you previously downloaded.
9- Boot the device.
PS
Always avoid minitools such as kingroot and stuff like that ? trust your terminal ?
seanwlk said:
Here's a small guide that recaps the method I've used over the years.
*Warning* You will need to unlock your bootloader, which will factory reset your phone
1- Download and install fastboot and USB drivers https://drive.google.com/file/d/0B9fZIF6vzIBzT2ZtZkNSVFI5ZHc/view?usp=drivesdk
This is a all-in-one installer I found a long while ago and I keep it in my drive to have it always available wherever I go. Say yes to all the prompts. And reboot the PC just in case.
2- Download Twrp and SuperSU
https://eu.dl.twrp.me/bacon/twrp-3.1.0-0-bacon.img.html
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
3- Backup all your data
4- Reboot your phone into bootloader and connect it to the PC.
5- Open a command prompt where you downloaded the twrp img file and type:
Code:
fastboot oem unlock
6- Now:
Code:
fastboot flash recovery twrp-3.1.0-0-bacon.img
(same name as the downloaded file)
7- Let the phone do the first boot.
8- Reboot into recovery flash the superSU zip you previously downloaded.
9- Boot the device.
PS
Always avoid minitools such as kingroot and stuff like that trust your terminal
Click to expand...
Click to collapse
Thanks so much for your help ! In step 3 when you say backup all your data, rather than copying all my pictures and contacts is there a quicker way? Do you use a program to backup an image of your phone that saves everything including text messages, contacts and pictures?
theaccountant87 said:
Thanks so much for your help ! In step 3 when you say backup all your data, rather than copying all my pictures and contacts is there a quicker way? Do you use a program to backup an image of your phone that saves everything including text messages, contacts and pictures?
Click to expand...
Click to collapse
I don't use any kind of software, I'm just organised, since I factory reset very often I keep stuff in the Download/Video/Image/Music folders and I copy them every time.
For the contacts I use google contacts which let's me sync across all the devices and save stuff without losing it in case of reset. Never saved a contact in my SIM.
I use only whatsapp and other IM apps that have their own backup online systems so I never lose anything but applications which I later downalod and install again.
seanwlk said:
I don't use any kind of software, I'm just organised, since I factory reset very often I keep stuff in the Download/Video/Image/Music folders and I copy them every time.
For the contacts I use google contacts which let's me sync across all the devices and save stuff without losing it in case of reset. Never saved a contact in my SIM.
I use only whatsapp and other IM apps that have their own backup online systems so I never lose anything but applications which I later downalod and install again.
Click to expand...
Click to collapse
Got it . Thanks again Sean. I'll give it a shot later on tonight!
theaccountant87 said:
Got it . Thanks again Sean. I'll give it a shot later on tonight!
Click to expand...
Click to collapse
Good luck ? it's not hard as it seems
Hi Sean,
i'm stuck on: 8- Reboot into recovery flash the superSU zip you previously downloaded.
I have the zip file in my sdk platform tools folder and in CMD prompt I put:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
adb push UPDATE-SR3-SuperSU-v2.79-SR3-20170114223742.zip /sdcard/
I get
adb: error: failed to get feature set: no devices/emulators found
I tried to manually copy the SuperSu zip file into my device but when I connect my OnePlus I can't see it being connected to my computer?!
I'm a little worried because my phone is unusable as of now and just in recovery mode
theaccountant87 said:
Hi Sean,
i'm stuck on: 8- Reboot into recovery flash the superSU zip you previously downloaded.
I have the zip file in my sdk platform tools folder and in CMD prompt I put:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
adb push UPDATE-SR3-SuperSU-v2.79-SR3-20170114223742.zip /sdcard/
I get
adb: error: failed to get feature set: no devices/emulators found
I tried to manually copy the SuperSu zip file into my device but when I connect my OnePlus I can't see it being connected to my computer?!
I'm a little worried because my phone is unusable as of now and just in recovery mode
Click to expand...
Click to collapse
You can mount the phone as MTP from the twrp recovery in the advanced settings, and then you'll be able to copy the files inside.
What do you mean with unusable? If you did as I wrote everything should be fine.
Just in case if the phone bootloops or it's stuck in the bootlogo, from the recovery wipe cache dalvik and data.
NOTE.
First boot can take a while, mine once lasted 30min after I clean fresh installed a ROM
EDIT
You don't need to move to the SDK folder on the cmd, the tool I made you Install works system wide from every folder, that's why I love it.
Hey All,
This is my first ever post on XDA ,So forgive me if I have not done a good job. I will try my best to provide sufficient details on how to upgrade LG urbane 2nd Edition Verizon model watch to Android wear 2.0 from Android wear 1.5
Known Issues : **********Android Pay is not working as reported by few users ***********
YOU FLASH THESE FILES AT THE RISK OF BRICKING YOUR DEVICE. I AM SIMPLY PROVIDING THEM AND BEAR NO RESPONSIBILITY FOR ANY SUBSEQUENT DAMAGE FROM FLASHING THESE FILES. ALL DATA ON THE PHONE WILL BE ERASED.
Prerequisites:
[*]LG Urbane 2nd Edition Verizon Model (W200V) for all other model you should have received a OTA by now , Please check OTA software updates on you watch.
[*]ADB tools ( Minimal is also sufficient) google for files and install in your computer , in my case I did it in "C:\adb".
[*]twrp-3.1.1.0 (twrp-3.1.1.0.img) recovery Image Copy of the file :- https://drive.google.com/drive/folders/0Bzk4DPXefDhrRzl3ckh6Uzhad1k
[*]Android Wear 2.0 OTA udpate Copy of the file :- [*]Modified file link http://www.filehosting.org/file/details/699795/lg2.zip or original file https://android.googleapis.com/pack.../af88cfbc96ad65e7b728e27c2decbdc6fb0e08e8.zip
[*]notepad++ (to edit updater-script), You can use Notepad as well.
1)perform factory reset on your watch just to be on safer side.
**update** Few users have reported that they have faced error while flashing due to buggy USB cable and they could successfully overcome the error by holding the cable to the watch and making sure the cable is fully in contact with the watch while flashing .**Update**
2)now we need to modify the OTA update file to work with Verizon model W200V ( skip this step if you have downloaded modified zip file and jump to 3rd step)
unzip the 'af88cfbc96ad65e7b728e27c2decbdc6fb0e08e8.zip" downloaded earlier and Browse the folder Edit file (updater-script) the file can be fount in the below path in my case."C:\ADB\af88cfbc96ad65e7b728e27c2decbdc6fb0e08e8\META-INF\com\google\android\updater-script". Use Notepad ++ and open the file and Remove 2 first rows,The file should start from "ui_print...", I used Note++ to edit the file and saved, as mentioned earlier you can use notepad as well.
Now Zip All files And name LG2.zip(Note : don't put all the files into a single folder and then zip, The zip should contain "META-INF" and other files) and place it in "C:\ADB\LG2.zip" for easier navigation in Cmd. (this file can be downloaded using above link Modified file")
3)next Connect your LG Urbane 2nd Edition watch to Computer and Enable ADB Debugging On watch (Settings-About-Tap about 8 times on "Build Number" and now go back to Setting and scroll down you should see new options "Developer Options" , Tap on "Developer Options" - and "ADB Debugging" select "Enable always from this computer" or something like that !!)
4)Now Check if your device has a connection to your computer using ADB tools
now on your computer under "Run" , type Cmd, this will bring windows command prompt.
Open Cmd in Windows and browse to ADB tools folder in my case I have placed ADB tools and all required files under "C:\abd"
Type "adb devices"
your device should show up under "List of devices attached"
Once device is found by computer we have to push the TWRP recover image to phone , To make life easy , I have downloaded all the above mentioned files to "C:\adb" folder
"adb push twrp-3.1.1.0 /sdcard/"
later boot into bootloader
"adb reboot bootloader"
Unlock bootloader
"fastboot oem unlock"
5)Now flash TWRP recovery (because we will be changing/modifying the original the OTA update file, stock recovery will fail to verify signature)
"fastboot flash recovery twrp-3.1.1.0.img"
boot to recovery to perform OTA side load
"fastboot reboot recovery"
Now you should see TWRP recovery welcome page,Allow read and write partition permission in TWRP.
6)now on your phone you should be in TWRP Main screen , press Install and you will find option to adb Sideload select that option and you will be presented with a option to wipe Dalvik and Wipe Cache , Select that and now go back to your cmd and type below code.
"adb sideload lg2.zip"
Now sit back and relax , The system will starts loading Android Wear2.0 to your verizon LG urbane 2nd edition watch (W200V) and once the process is finished , reboot to system.
1st boot will take some time , Have patience !! after all you have done ever thing right till now. (approx 5-10 mins, sometimes 15 mins)
Now your watch has Android wear 2.0 , enjoy.
Initially it might feel the OS is slow but allow the OS to settle down after that its snappy and the battery backup is also good in my opinion.
If you want to restore Stock recovery image just in case if you don't like TWRP, then
download the below targz file and extrat recovery.img file , LG Urbane 2 stock recovery image.
Link ,
enable ADB options under settings similar what we performed earlier.
1) Boot into bootloader
"adb reboot bootloader"
Stock Android wear 1.5 for LG Urbane 2nd Edition LTE(extract the file and copy recovery.img file to your folder , https://storage.googleapis.com/andr...wear-preview/nemo-mfd18l-factory-3faf6f2d.tgz (The file extension is */tgz(targz) , use 7zip application to extract the files and you will see recovery.img file .
Place a copy of recovery.img in "C:\adb\recovery.img"
"fastboot flash recovery recovery.img"
You can also Lock Bootloader to avoid the Notification at each boot.
"fastboot oem lock"
To get back to original android watch wear 1.5
if you don't like Android wear 2.0 use the below link and follow instruction to revert back to Android wear 1.5.
Stock Android wear 1.5 for LG Urbane 2nd Edition LTE , https://storage.googleapis.com/andr...wear-preview/nemo-mfd18l-factory-3faf6f2d.tgz (The file extension is */tgz(targz) , use 7zip application to extract the files.
Extract the *.tgz(targz) into your folder ("C:\adb")
Perform a "fastboot oem unlock", then run "flash-all.bat". Afterwards, you can "fastboot oem lock". This should restore you back to 1.5, where you need to take 1 OTA (from June 2016 Patch to December 2016 Patch).
Thanks All,
Missed something
Tried a thousand times. Not working **update** Looks like maybe It was just a buggy USB. I held it to the watch while flashing and it finally worked! I'm curious to hear anyone else's experiences with this cause it seems buggy but what would you expect? My apologies ty!
Has anyone other than the original poster tried this guide and been successful?
Thxfctr said:
Tried a thousand times. Not working
Click to expand...
Click to collapse
Are you getting any specific error ?
djdubd said:
Has anyone other than the original poster tried this guide and been successful?
Click to expand...
Click to collapse
It does work I had problems but I think holding the USB to the watch helps. I tried it a lot but it was worth it. Suck it verizon!
Thxfctr said:
Tried a thousand times. Not working **update** Looks like maybe It was just a buggy USB. I held it to the watch while flashing and it finally worked! I'm curious to hear anyone else's experiences with this cause it seems buggy but what would you expect? My apologies ty!
Click to expand...
Click to collapse
I am Glad finally it worked for you!!
suresh.chikkanna said:
I am Glad finally it worked for you!!
Click to expand...
Click to collapse
Ty! I think my USB connector is just a bit jinky.
I'm going to give this a try soon, everything working like lte, messages+, and phone?
Almost got it working
Followed all the directions and all seemed to work ok without errors. However, on startup now the watch is stuck on the startup splash screen (the animated google logo, has stayed there for hours). Can still access fastboot but unable to connect via ADB since the OS is not starting fully.
I also tried to restore back to 1.5 but since i can only access fastboot, my only option is to sideload but wont work with the TGZ link above.
Anyone have any ideas? or the zip file I could use to sideload the stock Wear1.5?
Thanks
Just making sure !! Try force restarting the watch by holding power button.
Did you reset the watch before sideloading ?
On android wear 1.5 use 7zip and unzip the tgz file and browse the folder till you see flashall bat file and run the same in bootloader. I have tried it and it works. Let us know if your still facing issues.
Locked /data won't allow sideload.
Hi, I've installed twrp, but it fails to sideload LG2.zip as the /data can't be mounted as it is encrypted. The TWRP doesn't have a format option for the /data partition so I can't reformat it to delete the encryption. So I'm stuck in TWRP.
Gphoton31 said:
Hi, I've installed twrp, but it fails to sideload LG2.zip as the /data can't be mounted as it is encrypted. The TWRP doesn't have a format option for the /data partition so I can't reformat it to delete the encryption. So I'm stuck in TWRP.
Click to expand...
Click to collapse
I had similar issue initially , had to restore back to 1.5 and then clean all the data and then sideload 2.0 back. Try that and let us know if that worked.
You are the man! That worked
Installed recovery.img bootloader, then ran the 1.5 bat file, then reinstalled twrp. /data unlocked and mounted, sideloaded 2.0. You turned my brick back into a watch. Thank you very much.
suresh.chikkanna said:
Just making sure !! Try force restarting the watch by holding power button.
Did you reset the watch before sideloading ?
On android wear 1.5 use 7zip and unzip the tgz file and browse the folder till you see flashall bat file and run the same in bootloader. I have tried it and it works. Let us know if your still facing issues.
Click to expand...
Click to collapse
Thanks.
I made sure to reset before force restart and reset before sideloading. Still having some trouble with the 1.5 reset though.
In bootloader, which option to I select for flashall to work? ADB Devices can't see it and if i just run from bootloader home screen i get , <waiting for any device>. Same thing in TWRP.
Thanks again for your help
[Note for other users unfamiliar with this process & having similar problems - you'll have to unzip the source file, then unzip "output" to extract all the files... tooke me a few attempts to realize i missed a step!]
Solved flash-all not working
OzzieJez said:
Thanks.
I made sure to reset before force restart and reset before sideloading. Still having some trouble with the 1.5 reset though.
In bootloader, which option to I select for flashall to work? ADB Devices can't see it and if i just run from bootloader home screen i get , <waiting for any device>. Same thing in TWRP.
Thanks again for your help
[Note for other users unfamiliar with this process & having similar problems - you'll have to unzip the source file, then unzip "output" to extract all the files... tooke me a few attempts to realize i missed a step!]
Click to expand...
Click to collapse
As with some other users the cable connection seemed to be causeing me some problems. I used a different USB port and held the connector against the watch and flashing to 1.5 worked this time.
---------- Post added at 06:37 PM ---------- Previous post was at 06:05 PM ----------
OzzieJez said:
Thanks.
I made sure to reset before force restart and reset before sideloading. Still having some trouble with the 1.5 reset though.
In bootloader, which option to I select for flashall to work? ADB Devices can't see it and if i just run from bootloader home screen i get , <waiting for any device>. Same thing in TWRP.
Thanks again for your help
[Note for other users unfamiliar with this process & having similar problems - you'll have to unzip the source file, then unzip "output" to extract all the files... tooke me a few attempts to realize i missed a step!]
Click to expand...
Click to collapse
As with some other users the cable connection seemed to be causeing me some problems. I used a different USB port and held the connector against the watch and flashing to 1.5 worked this time.
Gphoton31 said:
Installed recovery.img bootloader, then ran the 1.5 bat file, then reinstalled twrp. /data unlocked and mounted, sideloaded 2.0. You turned my brick back into a watch. Thank you very much.
Click to expand...
Click to collapse
I am really happy for you.
OzzieJez said:
Thanks.
I made sure to reset before force restart and reset before sideloading. Still having some trouble with the 1.5 reset though.
In bootloader, which option to I select for flashall to work? ADB Devices can't see it and if i just run from bootloader home screen i get , <waiting for any device>. Same thing in TWRP.
Thanks again for your help
[Note for other users unfamiliar with this process & having similar problems - you'll have to unzip the source file, then unzip "output" to extract all the files... tooke me a few attempts to realize i missed a step!]
Click to expand...
Click to collapse
Flash the original recovery.img extracted from the .tgz file and try again it should work.
For ADB access in TWRP use sideload using ADB option .
So will android pay work now with this
B
OzzieJez said:
Thanks.
I made sure to reset before force restart and reset before sideloading. Still having some trouble with the 1.5 reset though.
In bootloader, which option to I select for flashall to work? ADB Devices can't see it and if i just run from bootloader home screen i get , <waiting for any device>. Same thing in TWRP.
Thanks again for your help
[Note for other users unfamiliar with this process & having similar problems - you'll have to unzip the source file, then unzip "output" to extract all the files... tooke me a few attempts to realize i missed a step!]
Click to expand...
Click to collapse
I think I am having the same issue as you. I was sideloading 2.0 as instructed and I think I had a bad cable connection. I am now stuck with no wear operating system at all. When I start my phone it only stays on LG boot screen with the unlock icon on the bottom. My computer is now unable to recognize the device because I cannot get into settings to turn on ADB Debugging. If I follow the same steps as you can I sideload wear 1.5 and update via boot loader screen?
I think I am having the same issue as you. I was sideloading 2.0 as instructed and I think I had a bad cable connection. I am now stuck with no wear operating system at all. When I start my phone it only stays on LG boot screen with the unlock icon on the bottom. My computer is now unable to recognize the device because I cannot get into settings to turn on ADB Debugging. If I follow the same steps as you can I sideload wear 1.5 and update via boot loader screen?