Bootloader unlocking theory - Sprint LG G4

Agimax recently discovered a way into fast boot mode
Agimax said:
Ok, so i've been able to nuke my LAF partition and get into Fastboot mode. This gives access to all fastboot commands, but removes ability to use Download Mode. I am on ZV6 / UltraPOP. Once you backup your laf partition, you can reboot like you would for download mode but goes to fastboot. You can restore LAF partition from the backup you make and get back access to download mode.
I tried to see if our bootloader will unlock like the way they do it in the T-Mobile forums by checking the OEM Unlock in the developer menu, then booting to Fastboot and running 'Fastboot.exe oem unlock', but unfortunately it will not work. The phone does not recognize the unlock command like it does for the T-Mobile versions. See screenshots. I'm still working on this. Keep in mind, if you do something wrong, you will NOT have the ability to TOT without the download mode until you restore the LAF back to the phone!
Instructions: (only try if you are an advanced tester!)
1.) Backup your LAF partition command from ADB
* copy this in a safe place before nuking your LAF partition. Like on a flashdrive or computer.
Code:
dd if=/dev/block/bootdevice/by-name/laf of=/sdcard/laf.img
2.) Nuke your LAF partition command from ADB
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/laf
* now you can boot into fastboot mode by booting like you would into download mode (up-volume and power on with usb plugged in)
Note: Once you are in fastboot mode, you must update the drivers on your computer by opening device manager and clicking on the ADB device and updating driver over internet. Reboot back into fastboot mode and commands will work.
To restore your LAF partition command from ADB
Code:
'dd of=/dev/block/bootdevice/by-name/laf if=/sdcard/laf.img'
* you may also restore the laf partition from fastboot if you wish, but they are different commands
My thoughts are -if we were able to Nuke the LAF partition on 6.0 M, we would be able to copy the partitions from the phone we would need to make rooted system images and also modem and kernel. This should allow us to copy partitions to a phone running 5.1 and switch between by just flashing the 3 partitions back and forth.
Click to expand...
Click to collapse
Im wondering if we can get the unlock files from one of the other models and hexing out the unlock bin from imei numbers and zeros, maybe we can unlock our device by replacing them with our imei and serial number??

Who knows. I'm not a developer so maybe someone can try it. There's just not enough attention from developers for this device.

LaughingCarrot said:
Who knows. I'm not a developer so maybe someone can try it. There's just not enough attention from developers for this device.
Click to expand...
Click to collapse
That is some constructive feedback...

jaxbierley said:
That is some constructive feedback...
Click to expand...
Click to collapse
Just throwing something in to make conversation is all.

sorry to bothering you meaby would be better if you post all your unlock bootloader ideas on lg4 general forum...http://forum.xda-developers.com/g4/general where are more people to see it.

Awesomeslayerg said:
Agimax recently discovered a way into fast boot mode
Im wondering if we can get the unlock files from one of the other models and hexing out the unlock bin from imei numbers and zeros, maybe we can unlock our device by replacing them with our imei and serial number??
Click to expand...
Click to collapse
it's safe to nuke recovery and get the same result....so if anything does wrong you still have download mode!!!!

Any idea yet why the command "fastboot flashing unlock" is not recognized? It seems no commands are recognized...

thetruejay20 said:
Any idea yet why the command "fastboot flashing unlock" is not recognized? It seems no commands are recognized...
Click to expand...
Click to collapse
Its killing me not having fastboot. i have backed up all my bootloader partitions and have been skimming through trying to get my device id no. I have a random unlock.bin but that dont help none realy. All it doez is give me the hex adresse that are modified. But there diffrent on every one. From what it get is that the bootloader aint no more locked than any other. The partitions that the boooader resides in are what the issue is. they are encrypted i guess with a 256 bit security. From what i have read the unlock.bin decrypts the partitions so oem unlock can be applied. Now if im wrong or been misinformed please somone correct me.

TheMadScientist420 said:
Its killing me not having fastboot. i have backed up all my bootloader partitions and have been skimming through trying to get my device id no. I have a random unlock.bin but that dont help none realy. All it doez is give me the hex adresse that are modified. But there diffrent on every one. From what it get is that the bootloader aint no more locked than any other. The partitions that the boooader resides in are what the issue is. they are encrypted i guess with a 256 bit security. From what i have read the unlock.bin decrypts the partitions so oem unlock can be applied. Now if im wrong or been misinformed please somone correct me.
Click to expand...
Click to collapse
Yes I spent hours reading up on it yesterday, you're pretty much right on.

thetruejay20 said:
Yes I spent hours reading up on it yesterday, you're pretty much right on.
Click to expand...
Click to collapse
Now i found a tool windroid toolkit check it out i atempt to use the tool and it attemps to reboot me to fastboot i guess to attempt to get me identifier key but ofcoarse the phone just reboots. I guess i need to nuke my laf and try to see if i can get that key from my own device. My prob is im not to good with dd comands im rusty been a while. I have a backup of my laf cant find the post that shows me how to nuke and restore when im done testing is the instructions at top rite on doing it
---------- Post added at 11:58 AM ---------- Previous post was at 11:53 AM ----------
Im assuming that the toolkit prob uses a diffrent algorothim than g4 does to do unlocks but it asks what type of phone i click g4 never asks for a sub model
---------- Post added at 12:01 PM ---------- Previous post was at 11:58 AM ----------
And this is y lg needs to unlock them here we go trying extremes because of them.
---------- Post added at 12:33 PM ---------- Previous post was at 12:01 PM ----------
I guess we need to figure out how sprint lcked us out of fastboot. Thats the first step im back on it im at work rite now. So i aint got my comput near me.

TheMadScientist420 said:
I guess we need to figure out how sprint lcked us out of fastboot. Thats the first step im back on it im at work rite now. So i aint got my comput near me.
Click to expand...
Click to collapse
God speed to you man. I would love to pitch in, but I have no clie on how to crack a bootloader. Is there anything anywhere that I can learn from?

Quickdraw996 said:
God speed to you man. I would love to pitch in, but I have no clie on how to crack a bootloader. Is there anything anywhere that I can learn from?
Click to expand...
Click to collapse
I have been readin up on old lg bootloaders i use to to a lotta nes roms hack which is differ of coarse but. They do hex edit to mod them. Biggest think is craking the 256 bit encryption. Only thing i ask of any of u is read and inform me too we can hopefully figure this out. I aint no dev but anything is possible the solution is sometimes the dumbest thing rite in front of u. Were looking so deep that it might be rite in front of our faces. I. Need to get to fastboot without nuking my laf partition i need it working. Trying to figure how sprint locked us out of fast boot

TheMadScientist420 said:
I have been readin up on old lg bootloaders i use to to a lotta nes roms hack which is differ of coarse but. They do hex edit to mod them. Biggest think is craking the 256 bit encryption. Only thing i ask of any of u is read and inform me too we can hopefully figure this out. I aint no dev but anything is possible the solution is sometimes the dumbest thing rite in front of u. Were looking so deep that it might be rite in front of our faces. I. Need to get to fastboot without nuking my laf partition i need it working. Trying to figure how sprint locked us out of fast boot
Click to expand...
Click to collapse
Well I nuked my recovery partition to get into fastboot mode, but no fastboot commands are recognized in fastboot mode.
---------- Post added at 03:57 PM ---------- Previous post was at 03:52 PM ----------
TheMadScientist420 said:
Now i found a tool windroid toolkit check it out i atempt to use the tool and it attemps to reboot me to fastboot i guess to attempt to get me identifier key but ofcoarse the phone just reboots. I guess i need to nuke my laf and try to see if i can get that key from my own device. My prob is im not to good with dd comands im rusty been a while. I have a backup of my laf cant find the post that shows me how to nuke and restore when im done testing is the instructions at top rite on doing it
---------- Post added at 11:58 AM ---------- Previous post was at 11:53 AM ----------
Im assuming that the toolkit prob uses a diffrent algorothim than g4 does to do unlocks but it asks what type of phone i click g4 never asks for a sub model
---------- Post added at 12:01 PM ---------- Previous post was at 11:58 AM ----------
And this is y lg needs to unlock them here we go trying extremes because of them.
---------- Post added at 12:33 PM ---------- Previous post was at 12:01 PM ----------
I guess we need to figure out how sprint lcked us out of fastboot. Thats the first step im back on it im at work rite now. So i aint got my comput near me.
Click to expand...
Click to collapse
I checked out that windroid toolkit, and the only supported LG G4 devices is the H815. But definitely a good find!

Related

Stock RUU's Download Here >

​
This is an update on a previous post, this time however you don't have to sieve through Chinese websites to get them....i have spent time to get them for you!
This Will revert your HTC Salsa to Stock​​
By using these you will wipe everything you have done. Recovery will be wiped, unknown about lock/unlocked boot-loader as i haven't attempted this with unlocked boot-loader before as.i had s-off at the time.
You do this at your own risk, i take no responsibility at all for anything that may or may not happen lol​​
Instructions for use.
HTC SYNC installed but not running, you want the cable driver mainly.
Instead of following on screen instruction via the RUU, set your phone into fastboot mode yourself then activate/run the RUU.exe you require, i would suggest run as administrator (right click on application)
This will take some time to install, i did it on 3rd attempt, first 2 were relying on the RUU to boot the phone for me...3rd i booted into fastboot/bootloader myself and away it went.
if for any reason it doesn't respond to you or it doesn't install stock or freezes, whip out the battery and do it all again!
Below are the RUU's please find the correct region your in and download accordingly. EU RUU is a common one if the others don't work. all roms are based of this version.
RUU_Icon_G_HTCCN_CHS_1.24.1400.4_Radio_47.14.35.3030H_7.47.35.17_release_204455_signed.exe
RUU_Icon_G_HTC_Europe_1.12.401.1_R_Radio_47.14.35.3030H_7.47.35.17_release_193257_signed.exe
RUU_Icon_G_O2_UK_1.18.206.2_Radio_47.14.35.3030H_7.47.35.17_release_198160_signed.exe
RUU_Icon_G_hTC_Asia_HK_1.16.708.3_Radio_47.14.35.3030H_7.47.35.17_release_197702_signed.exe
RUU_Icon_G_hTC_Asia_India_1.12.720.2_Radio_47.14.35.3030H_7.47.35.17_release_193467_signed.exe
RUU_Icon_G_HTC_TUR_1.18.468.2_Radio_47.14.35.3030H_7.47.35.17_release_199341_signed.exe
RUU_Icon_G_Hutch_AUS_1.18.861.1_Radio_47.14.35.3030H_7.47.35.17_release_197619_signed.exe
RUU_Icon_G_Voda-Hutch_AU_1.17.862.2_Radio_47.14.35.3030H_7.47.35.17_release_198433_signed.exe
RUU_Icon_G_Chunghwa_1.13.751.1_Radio_47.14.35.3030H_7.47.35.17_release_193940_signed.exe
RUU_Icon_G_hTC_Asia_WWE_1.12.707.2_Radio_47.14.35.3030H_7.47.35.17_release_193464_signed.exe
as the link in the lower post suggested you can also try this
*this wasn't provided by me please don't blame me if anything goes wrong*
1. Download your RUU
2. Extract and copy the system.img AND boot.img to the same directory as your fastboot tools "C:/fastboottools" ( make sure to copy both files )
3. Enter the fastboot mode on your phone by pressing volume down + power button after the device has been turned off.
4. Choose fastboot on the phone by pressing power button, and then connect your phone to your PC
5. Using fastboot tools, open the Command prompt and navigate to "C:\fastboottools" then run this command on cmd: "fastboot flash system system.img"
6. Dont reboot, Using fastboot tools, run this command on cmd: "fastboot flash boot boot.img"
( The two commands in step 5 and 6 are different, make sure to type each one correctly and to do them straight after each other )
7. Reboot phone. let it boot up, you will still get bootloop or error message.
8. Take out the battery.
9. Boot back into bootloader ( Volume down + power ).
10. Now choose recovery.
11. Phone should now reboot itself and bam, all should now work fine.​
Well it seems a lot of you shadows hiding away wanted these lol, as the downloads in 1 day surprised me lol.
BigBear is using Xparent Tapatalk Purple
I managed to revert back to stock using this method http://forum.xda-developers.com/showthread.php?t=1631121
Now I am running 2.3.3
Now i just want to update to 2.3.5 if possible, haven't been able to get OTA updates. Do you know how i can go about it?
CWM recovery is still intact.
Thanks
The salsa will never have 2.3.5 ota. HTC stopped at 2.3.3 and discontinued updates for us. well the stopped producing the salsa and totally dropped it.
that's why we have 2.3.5 roms that are not meant for us...ie no FB button that works correctly, no mirror or front facing camera.
and this is probably why noone is still running stock roms anymore
BigBear is using Xparent Tapatalk Purple
getting error 155 again and again. Used RUU_Europe, RUU_UK, RUU_Asia_WWE, RU_Asia_India. Rebooted to the fastboot screen myself but the RUU takes over from the white screen and fastboot menu and goes into the black screen with HTC written. Tried letting RUU boot itself but still same error.
EDIT:
I have previously unlocked bootloader to gain Root Access since I had S-ON on my device. Need help urgently. Can I revert back to a locked Bootloader or anything ?
Now I have relocked the bootloader and tried the Europe Salsa RUU.... It is giving me Error 140 now claiming the bootloader version is invalid.
HBOOT is updated and I notice that the Radio version mentioned on Fastboot Bootloader screen is different than mentioned in the RUU.
Mine says:
*** Relocked ***
ICON_G PVT SHIP S-ON RL
HBOOT-1.08.0000
MICROP-0558
RADIO-7.51.35.19
Dec 16 2011,16:12:07
razasohail said:
getting error 155 again and again. Used RUU_Europe, RUU_UK, RUU_Asia_WWE, RU_Asia_India. Rebooted to the fastboot screen myself but the RUU takes over from the white screen and fastboot menu and goes into the black screen with HTC written. Tried letting RUU boot itself but still same error.
EDIT:
I have previously unlocked bootloader to gain Root Access since I had S-ON on my device. Need help urgently. Can I revert back to a locked Bootloader or anything ?
Click to expand...
Click to collapse
Did you take a nandroid backup in recovery at all?, if so restore it.if recovery isn't there reinstall recovery and restore your backup.
BigBear is using Xparent Tapatalk Purple
Get the phone to Stock
Hi..
Where can I get these files
system.img and boot.img
2. Extract and copy the system.img AND boot.img to the same directory as your fastboot tools "C:/fastboottools" ( make sure to copy both files )
arekapudi said:
Hi..
Where can I get these files
system.img and boot.img
2. Extract and copy the system.img AND boot.img to the same directory as your fastboot tools "C:/fastboottools" ( make sure to copy both files )
Click to expand...
Click to collapse
this guide wasn't provided by me, i do know what this means but its hard to explain to a newbie...
for the more technical side of go here >http://forum.xda-developers.com/showthread.php?t=1631121, it may help you...
ok after of hours of fiddling around with this, I have come to the point where I really need the system.img and boot.img files
my phone is stuck at the htc boot screen with white background.
I have installed htc cable driver and got fastboottools files created and did some googling and found out that the only other way to install this is by running the exe while in fastboot and have to bootloader "relocked"
I tried to extract them from the executable using 7-zip but can't see them there.
Any help is greatly appreciated. thanks.
Saturn007 said:
ok after of hours of fiddling around with this, I have come to the point where I really need the system.img and boot.img files
my phone is stuck at the htc boot screen with white background.
I have installed htc cable driver and got fastboottools files created and did some googling and found out that the only other way to install this is by running the exe while in fastboot and have to bootloader "relocked"
I tried to extract them from the executable using 7-zip but can't see them there.
Any help is greatly appreciated. thanks.
Click to expand...
Click to collapse
in all fairness mate, i can't help on this. these guides were provided by others and has been known to work for us. i have not tried this and will not be trying this either as i have no desire to revert. what i do mention in all rom threads is this. take a backup of your stock rom in recovery before you tamper or change anything, this way you can revert straight back to your stock rom, no questions asked.
i would think though you may not have either installed correctly or its the wrong ruu, but i can't tell
BigBearEvo said:
in all fairness mate, i can't help on this. these guides were provided by others and has been known to work for us. i have not tried this and will not be trying this either as i have no desire to revert. what i do mention in all rom threads is this. take a backup of your stock rom in recovery before you tamper or change anything, this way you can revert straight back to your stock rom, no questions asked.
i would think though you may not have either installed correctly or its the wrong ruu, but i can't tell
Click to expand...
Click to collapse
I am not holding you responsible for any of my actions mate. I do appreciate all the info you provided here.
I attempted to do a backup but the SD card got full in the middle of the process. My luck.
I was just asking if anyone (not necessarily you) would have a copy of these files as I attempted to download the files from the other thread, http://forum.xda-developers.com/showthread.php?t=1631121, but the links are dead. I was hoping someone might have them and would like to share with us. That's all.
Saturn007 said:
I am not holding you responsible for any of my actions mate. I do appreciate all the info you provided here.
I attempted to do a backup but the SD card got full in the middle of the process. My luck.
I was just asking if anyone (not necessarily you) would have a copy of these files as I attempted to download the files from the other thread, http://forum.xda-developers.com/showthread.php?t=1631121, but the links are dead. I was hoping someone might have them and would like to share with us. That's all.
Click to expand...
Click to collapse
tel me what you want and ill get it, but you have to tell me which file to get it from and ill host it up for you. ie you want the system.img and boot.img but from which ruu?
BigBearEvo said:
tel me what you want and ill get it, but you have to tell me which file to get it from and ill host it up for you. ie you want the system.img and boot.img but from which ruu?
Click to expand...
Click to collapse
Hi i am getting error 140 aswell after relocking my bootloader..???can someone help me as im trying to restore and im struggeling...
any help will be appreciated but i tried some other tutorials but they require a zip version of the RUU.. ;(
gagan313 said:
Hi i am getting error 140 aswell after relocking my bootloader..???can someone help me as im trying to restore and im struggeling...
any help will be appreciated but i tried some other tutorials but they require a zip version of the RUU.. ;(
Click to expand...
Click to collapse
you won't get a zip version ruu only stock as i listed rom wise. now did you lock the bootloader before trying to add stock back on?
if you did there's part of your problem.
unlock it again, go find stock.zip in stock rom thread in android development section and flash it....then lock the bootloader. if you lock the loader again please note root etc won't work/function correctly again. to have any root privilege's you require either s-off or unlocked bootloader.
BigBearEvo said:
you won't get a zip version ruu only stock as i listed rom wise. now did you lock the bootloader before trying to add stock back on?
if you did there's part of your problem.
unlock it again, go find stock.zip in stock rom thread in android development section and flash it....then lock the bootloader. if you lock the loader again please note root etc won't work/function correctly again. to have any root privilege's you require either s-off or unlocked bootloader.
Click to expand...
Click to collapse
ok i will try that now
---------- Post added at 09:53 PM ---------- Previous post was at 09:41 PM ----------
nope... it dosnt work... it says bootloader version error
(which came up before..)
just so you know.. i am S-ON and hboot 1.8.00000 or somthing...
---------- Post added at 10:34 PM ---------- Previous post was at 09:53 PM ----------
could it be posssible that i have the wrong RUU??
i am definatly on EURO but when i go through the ruu install wizard it says:
Verify that you want to update the ROM version:
From:
Image version:
1.28.0.0
To:
Image version:
1.12.401.1_r
could i have the wrong one?? or is this normal??
gagan313 said:
ok i will try that now
---------- Post added at 09:53 PM ---------- Previous post was at 09:41 PM ----------
nope... it dosnt work... it says bootloader version error
(which came up before..)
just so you know.. i am S-ON and hboot 1.8.00000 or somthing...
---------- Post added at 10:34 PM ---------- Previous post was at 09:53 PM ----------
could it be posssible that i have the wrong RUU??
i am definatly on EURO but when i go through the ruu install wizard it says:
Verify that you want to update the ROM version:
From:
Image version:
1.28.0.0
To:
Image version:
1.12.401.1_r
could i have the wrong one?? or is this normal??
Click to expand...
Click to collapse
tends to be normal that, but just to let you know...i have only ever reset using the ruu once before and it took along time to do it! since then ive never gone back. ive flashed stock.zip which gave me back stock...but its not for me.
so flash my stock.zip nothing else.
if it is just Facebook your having issues with then don't just swap roms or go back to stock, it won't help, it will probably make it worse to be honest. im using a new black Facebook as i hosted in the thread in android apps section and have no problems with it.
just make sure you have Facebook installed and moved to sd only.
BigBearEvo said:
tends to be normal that, but just to let you know...i have only ever reset using the ruu once before and it took along time to do it! since then ive never gone back. ive flashed stock.zip which gave me back stock...but its not for me.
so flash my stock.zip nothing else.
if it is just Facebook your having issues with then don't just swap roms or go back to stock, it won't help, it will probably make it worse to be honest. im using a new black Facebook as i hosted in the thread in android apps section and have no problems with it.
just make sure you have Facebook installed and moved to sd only.
Click to expand...
Click to collapse
thats just the thing you see....
for some reason, if i try the stock.zip i always have wifi issues as well as facebook issues and well... i have tried all the facebooks from 1.9.9 to the black one and it dosnt seem to sign in... evern after i have unin installed and moved to sd card using links2sd....:crying:
as for stock....
what i think is that there is a problem with my hboot... and error massage came up saying my hboot is newer than the one im trying to install... any way i can downgrade? (sorry for asking for so much of you)
gagan313 said:
that's just the thing you see....
for some reason, if i try the stock.zip i always have WiFi issues as well as Facebook issues and well... i have tried all the Facebook from 1.9.9 to the black one and it doesn't seem to sign in... even after i have uninstalled and moved to sdcard using link2sd....:crying:
as for stock....
what i think is that there is a problem with my hboot... and error massage came up saying my hboot is newer than the one im trying to install... any way i can downgrade? (sorry for asking for so much of you)
Click to expand...
Click to collapse
no way to downgrade sorry.
it has been noted elsewhere that this Facebook issue tends to fail when its installed on normal internal memory or as an update on-top of the system Facebook already installed.
you can tell if this is the case by going into link2sd and looking at Facebook.apk, it may have a green updated next to it. you can remove this update by uninstalling it.
i don't have this problem as it works fine on CM7.
you can try and uninstall the Facebook you have, go into recovery wipe cache/dalvik and reboot, apparently this removes all traces it was there.
reboot and install Facebook 2.0 or black which ever.
using link2sd move it to the sdcard and then try it.
i am gonna try this on other roms when i can to see if this works or not.
BigBearEvo said:
no way to downgrade sorry.
it has been noted elsewhere that this Facebook issue tends to fail when its installed on normal internal memory or as an update on-top of the system Facebook already installed.
you can tell if this is the case by going into link2sd and looking at Facebook.apk, it may have a green updated next to it. you can remove this update by uninstalling it.
i don't have this problem as it works fine on CM7.
you can try and uninstall the Facebook you have, go into recovery wipe cache/dalvik and reboot, apparently this removes all traces it was there.
reboot and install Facebook 2.0 or black which ever.
using link2sd move it to the sdcard and then try it.
i am gonna try this on other roms when i can to see if this works or not.
Click to expand...
Click to collapse
ok ill give it a shot

HTC One Bricked?

Ok so I recently rooted my HTC One and I think I might've bricked my phone. I tried out the Renovate ROM (I think it was the latest version) and it didn't work somehow, and my phone was stuck in boot, so I went into recovery, and factory reset but I accidently checked the button for system and then my OS was deleted. To fix that, I adb pushed Insert Coin ROM and flashed that, but when I booted my phone, it started up fine, but then after 10 seconds or so, the phone would just freeze and then reboot. I went back into recovery adb pushed the stock Sprint HTC One ROM and flashed that and the same thing is happening, but this time, when the phone turns on, it just shows a black screen with the notification bar at the top, and I can't use it in any way. It also freezes and reboots after like 10 second.
TL: DR
My Sprint HTC One keeps on freezing then rebooting after ten seconds, no matter what ROM I try.
Thanks in advance.
Yea....you understand you cant install gsm htc one roms. Thats what you did. Go download a ruu and run it while your in bootloader as i see adb is working for you
Sent from my HTCONE using xda premium
---------- Post added at 12:09 PM ---------- Previous post was at 11:57 AM ----------
Also no ur not bricked. A hard brick means the phone cant even power on. Its a brick. Unusable.
Sent from my HTCONE using xda premium
HTC_M7 said:
Yea....you understand you cant install gsm htc one roms. Thats what you did. Go download a ruu and run it while your in bootloader as i see adb is working for you
Sent from my HTCONE using xda premium
---------- Post added at 12:09 PM ---------- Previous post was at 11:57 AM ----------
Also no ur not bricked. A hard brick means the phone cant even power on. Its a brick. Unusable.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
I believe I have done the same thing as I am very new to this. Is there a link or something to find this ruu? and doesn't it need to be a certain one?
Like my phone is a Sprint HTC One. I am stuck in a boot loop and no matter what ROM I try it just keeps rebooting? Please any help would be greatly appreciated!
Check this thread for the RUU and instructions
http://forum.xda-developers.com/showthread.php?t=2250904
Khilbron said:
Check this thread for the RUU and instructions
http://forum.xda-developers.com/showthread.php?t=2250904
Click to expand...
Click to collapse
YESSSS!!!!!! Thank you it worked after following video instructions. Thanks again. You wouldnt know to unlock bootloader again with fast boot would you? Or would I need to follow Dev instructions again?
---------- Post added at 01:42 PM ---------- Previous post was at 01:28 PM ----------
Also what is a gsm htc one rom and how is it different sorry but like i said I am very new to this less than a week so any info I am sucking up like a sponge! Thanks again for your help!
Knixson said:
YESSSS!!!!!! Thank you it worked after following video instructions. Thanks again. You wouldnt know to unlock bootloader again with fast boot would you? Or would I need to follow Dev instructions again?
---------- Post added at 01:42 PM ---------- Previous post was at 01:28 PM ----------
Also what is a gsm htc one rom and how is it different sorry but like i said I am very new to this less than a week so any info I am sucking up like a sponge! Thanks again for your help!
Click to expand...
Click to collapse
fastboot flash unlocktoken Unlock_code.bin
GSM is the AT&T, T-mobile & international models....Sprint & Verizon are CDMA
O.M.J said:
fastboot flash unlocktoken Unlock_code.bin
GSM is the AT&T, T-mobile & international models....Sprint & Verizon are CDMA
Click to expand...
Click to collapse
Thank you! would I also need to install the open recovery twrp to gain root access as well?
Knixson said:
YESSSS!!!!!! Thank you it worked after following video instructions. Thanks again. You wouldnt know to unlock bootloader again with fast boot would you? Or would I need to follow Dev instructions again?
---------- Post added at 01:42 PM ---------- Previous post was at 01:28 PM ----------
Also what is a gsm htc one rom and how is it different sorry but like i said I am very new to this less than a week so any info I am sucking up like a sponge! Thanks again for your help!
Click to expand...
Click to collapse
You need to follow the dev instructions. If I were you though, I wouldn't do anything more until you understand some of the risks involved. A phone is a really, really inconvenient thing to have incapacitated when you're learning how to flash. For one, your device wasn't bricked (completely nonresponsive to input); for another, dev instructions are going to tell you to use fastboot (or a toolkit that runs fastboot for you).
Before you start again, you should learn how to use fastboot at the very least, and if you can, adb install/sideload (although it seems you tried that based on the OP). fastboot is often the only thing working if a flash goes awry.
A ROM is a ROM, no matter what device it's for. GSM/CDMA are separate network technologies that power your phone. In the U.S., Sprint and Verizon are the major CDMA carriers, while AT&T, T-Mobile, and essentially the rest of the world use GSM. The easiest way to tell the difference between the two is to remember if you needed a SIM card to activate the phone or not.
However, GSM and CDMA devices are set up differently on the software (and hardware, in terms of radios) side, and if you flash a ROM built for a GSM phone onto a CDMA equivalent, you'll probably break the device. For all intents and purposes, you should consider GSM phones to be wholly distinct devices. Also make sure you're only flashing ROMs built for Sprint, as there are often differences between Sprint and Verizon phones as well.
Knixson said:
Thank you! would I also need to install the open recovery twrp to gain root access as well?
Click to expand...
Click to collapse
yep...unlock, flash recovery, flash ROM
Rirere said:
You need to follow the dev instructions. If I were you though, I wouldn't do anything more until you understand some of the risks involved. A phone is a really, really inconvenient thing to have incapacitated when you're learning how to flash. For one, your device wasn't bricked (completely nonresponsive to input); for another, dev instructions are going to tell you to use fastboot (or a toolkit that runs fastboot for you).
Before you start again, you should learn how to use fastboot at the very least, and if you can, adb install/sideload (although it seems you tried that based on the OP). fastboot is often the only thing working if a flash goes awry.
A ROM is a ROM, no matter what device it's for. GSM/CDMA are separate network technologies that power your phone. In the U.S., Sprint and Verizon are the major CDMA carriers, while AT&T, T-Mobile, and essentially the rest of the world use GSM. The easiest way to tell the difference between the two is to remember if you needed a SIM card to activate the phone or not.
However, GSM and CDMA devices are set up differently on the software (and hardware, in terms of radios) side, and if you flash a ROM built for a GSM phone onto a CDMA equivalent, you'll probably break the device. For all intents and purposes, you should consider GSM phones to be wholly distinct devices. Also make sure you're only flashing ROMs built for Sprint, as there are often differences between Sprint and Verizon phones as well.
Click to expand...
Click to collapse
Thank you for all your information I really do appreciate it. I believe I understand fastboot alot better than when I started. I am starting to understand what I did wrong. I just have a few questions and I think I will be fine to just flash ROMs which is all I really want to do.
1. does it matter if s is off or not?
2. when I do flash a ROM should I flash just the IMG file or the whole ZIP?
I am sorry if this is inconvenient for you or other memebers I do apologize just trying to learn about this flashing ROMS
Knixson said:
Thank you for all your information I really do appreciate it. I believe I understand fastboot alot better than when I started. I am starting to understand what I did wrong. I just have a few questions and I think I will be fine to just flash ROMs which is all I really want to do.
1. does it matter if s is off or not?
2. when I do flash a ROM should I flash just the IMG file or the whole ZIP?
I am sorry if this is inconvenient for you or other memebers I do apologize just trying to learn about this flashing ROMS
Click to expand...
Click to collapse
1) If all you are doing is flashing Roms right now you don't need to s-off.
2) You flash the zip.
and I will second the notion that you should do a lot of reading before you do too much. This is an easy process to screw up if you don't know what you are doing and taking your phone out of commission can be a real pain in the ass.
Good Luck!
Knixson said:
Thank you for all your information I really do appreciate it. I believe I understand fastboot alot better than when I started. I am starting to understand what I did wrong. I just have a few questions and I think I will be fine to just flash ROMs which is all I really want to do.
1. does it matter if s is off or not?
2. when I do flash a ROM should I flash just the IMG file or the whole ZIP?
I am sorry if this is inconvenient for you or other memebers I do apologize just trying to learn about this flashing ROMS
Click to expand...
Click to collapse
We all have to start somewhere. There are some good guides in the forums if you search though that will be a lot more comprehensive than the answers we can give in each individual thread.
1. S-OFF matters if you want to make changes to /system during runtime. For example, if you used a root tool like Titanium Backup to move an app into /system with S-ON, the phone would crash because it detected a security violation (improper programic access to a secured location). S-OFF disables that check. You can still flash ROMs with S-ON though since the protection isn't active to the same extent in recovery, although I think it will block writing to the radio. Don't monkey with it more than you have to though, because it's easy to really screw yourself over with the wrong combination of software (unsigned boot software and S-ON will really brick your phone).
2. Read the thread. Almost all ROMs though are distributed in a flashable .zip, meaning you copy it over to the phone's storage and install through recovery (or use sideload). You shouldn't have to use the .imgs ever, although it's a good trick to know (use fastboot flash <> <>.img) in case something goes wrong. I had to do this recently when my fubared my /system but didn't feel like reflashing the whole ROM, so I extracted system.img from the ROM I used and just pushed that to device.
Rirere said:
We all have to start somewhere. There are some good guides in the forums if you search though that will be a lot more comprehensive than the answers we can give in each individual thread.
1. S-OFF matters if you want to make changes to /system during runtime. For example, if you used a root tool like Titanium Backup to move an app into /system with S-ON, the phone would crash because it detected a security violation (improper programic access to a secured location). S-OFF disables that check. You can still flash ROMs with S-ON though since the protection isn't active to the same extent in recovery, although I think it will block writing to the radio. Don't monkey with it more than you have to though, because it's easy to really screw yourself over with the wrong combination of software (unsigned boot software and S-ON will really brick your phone).
2. Read the thread. Almost all ROMs though are distributed in a flashable .zip, meaning you copy it over to the phone's storage and install through recovery (or use sideload). You shouldn't have to use the .imgs ever, although it's a good trick to know (use fastboot flash <> <>.img) in case something goes wrong. I had to do this recently when my fubared my /system but didn't feel like reflashing the whole ROM, so I extracted system.img from the ROM I used and just pushed that to device.
Click to expand...
Click to collapse
Thank you everyone has been very helpful I am so glad I found this forum I really do appreciate all the info that has been shared with me!
So I will leave with one final question then back to studying, Do you know any really good beginner tutorials or anything to start at?
Thanks again people I have learned a lot just in this conversation
Knixson said:
Thank you everyone has been very helpful I am so glad I found this forum I really do appreciate all the info that has been shared with me!
So I will leave with one final question then back to studying, Do you know any really good beginner tutorials or anything to start at?
Thanks again people I have learned a lot just in this conversation
Click to expand...
Click to collapse
There was a really good one in one of the threads in the development section, but I can't for the life of me remember what ROM had it posted. I'll take another look for it later, but in the meantime I would try reading on XDA's wiki.
Oh I just remembered one more question. I have Viper ROM currently but if I wanted to ad a different one should I wipe the Viper first and install new one or would it install right over top of the Viper? Thanks any help is appreciated. You have been the best!!!
Knixson said:
Oh I just remembered one more question. I have Viper ROM currently but if I wanted to ad a different one should I wipe the Viper first and install new one or would it install right over top of the Viper? Thanks any help is appreciated. You have been the best!!!
Click to expand...
Click to collapse
You can flash over it (which is often called a dirty flash) but you are much better off wiping first. I usually use This tool. Just put it on your sd card and flash it before you flash your new ROM.
I believe this thread will help any and all Sprint HTC One owners if they are having bootloop problems and also answers to frequently asked questions lmao!! Thanks again everyone you ALL have been VERY HELPFUL!!!!
Knixson said:
I believe this thread will help any and all Sprint HTC One owners if they are having bootloop problems and also answers to frequently asked questions lmao!! Thanks again everyone you ALL have been VERY HELPFUL!!!!
Click to expand...
Click to collapse
also do a nandroid before flashing, so you have a fall back
Htc One Stuck In Cwm And Cant Flash A Rom
SO i Rooted my Htc one and now im stuck in Cwm and i cant flash a rom or anything i have tried to sideload a Ruu file onto my phone but that didnt work
SO i tried using the Rom Update Utility and that didnt work either
Im lost and stuck with a Htc One That doesnt work at all i have tried multiple methods but nothing seems to work please help me if you can im 100% new to this whole thing....
jake012 said:
SO i Rooted my Htc one and now im stuck in Cwm and i cant flash a rom or anything i have tried to sideload a Ruu file onto my phone but that didnt work
SO i tried using the Rom Update Utility and that didnt work either
Im lost and stuck with a Htc One That doesnt work at all i have tried multiple methods but nothing seems to work please help me if you can im 100% new to this whole thing....
Click to expand...
Click to collapse
Check PM

Nexus 6 Flashing TEAMWIN STUCK?

I managed to borrow a Samsung Satellite laptop, so I could root and unlock my Nexus 6. Laptop is brand new. Everything was great on unlocking and rooting using Wogfresh's Nexus Tool Kit.
Then I decided to stop the forced encryption. Used Wug's Tool Kit again. At the end it says phone will reboot in 15 minutes. I waited over a half hour. Then I tried rebooting the phone. Now it flashed teamwin.
I can get it turned off. And I can still get it into recovery, bootloader mode, etc. I worked on this from 16:30 - 05:30 yesterday. I have been working today for another 3-4 hours.
Wug's Tool, the computer will not recognize the phone. Any help would be greatly appreciated. This is sooooo frustrating! I have uninstalled drivers, updated drivers, usbs too. I did everything Wug's kit said to do.
Sent from my SGH-I337 using Tapatalk
first off, stop using toolkits!
doing it properly is just as easy, and takes about 4-5 minutes, to unlock the bootloader, flash the recovery, flash the supersu zip, and to flash a custom kernel that wont bring on encryption(but you have format data for un-encryption to work).
Good looking out! Thanks for all the information. I am positive that you must be of Wug's caliber, dev wise, right?
It's a real shame everyone doesn't know everything like you, huh? Also appreciate the directions on doing it your way, in 4-5 minutes.
Sent from my SGH-I337 using Tapatalk
addcancercat said:
Good looking out! Thanks for all the information. I am positive that you must be of Wug's caliber, dev wise, right?
It's a real shame everyone doesn't know everything like you, huh? Also appreciate the directions on doing it your way, in 4-5 minutes.
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
assuming you got the driver installed..
1. while in bootloader.. fastboot oem unlock(this will unlock the bootloader
2. fastboot flash twrp recovery
3. flash the latest supersu with twrp recovery
this will give you root
4. flash any custom kernel(if you want to decrypt).
5. in twrp recovery, format data.
6. reboot and youll be rooted and unencrypted.
thats the basics, for any nexus. root toolkits can be used, if you already know what to do. if you are clueless of the process, youll learn ziltch using a roit toolkit, and will remain without any knowledge. so when you need to do some basic upkeep, you will be clueless, and will feel as your device is bricked. at that point youll start a pointless thread..
Thanks again. Did you read my post?
No I don't have drivers installed.
The computer does not recognize the phone now.
Please spare me anymore help.
Sent from my SGH-I337 using Tapatalk
simms22 said:
assuming you got the driver installed..
1. while in bootloader.. fastboot oem unlock(this will unlock the bootloader
2. fastboot flash twrp recovery
3. flash the latest supersu with twrp recovery
this will give you root
4. flash any custom kernel(if you want to decrypt).
5. in twrp recovery, format data.
6. reboot and youll be rooted and unencrypted.
thats the basics, for any nexus. root toolkits can be used, if you already know what to do. if you are clueless of the process, youll learn ziltch using a roit toolkit, and will remain without any knowledge. so when you need to do some basic upkeep, you will be clueless, and will feel as your device is bricked. at that point youll start a pointless thread..
Click to expand...
Click to collapse
Dude lay off! You are forever on here giving ppl **** about the posts they make. Sorry if most ppl arnt as skilled as you and might actually need some help. Just cause your "recognized" doesnt make you a mod. If they have a problem with what someone post let them deal with it.
addcancercat said:
Thanks again. Did you read my post?
No I don't have drivers installed.
The computer does not recognize the phone now.
Please spare me anymore help.
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
have you went through and installed it yet? here is the page for the android adb driver as well, it should also work http://adbdriver.com/
---------- Post added at 07:45 PM ---------- Previous post was at 07:41 PM ----------
chris6278 said:
Dude lay off! You are forever on here giving ppl **** about the posts they make. Sorry if most ppl arnt as skilled as you and might actually need some help. Just cause your "recognized" doesnt make you a mod. If they have a problem with what someone post let them deal with it.
Click to expand...
Click to collapse
lay off what? with helping him out? no, im not a mod, nor do i want to be a mod(i have said no to xda mod offers before). but, i will always fight against lies and untruth, no matter what, no matter who says it. i dont come here, to xda, to learn. i mostly come here to help people out. if you dont want any help, thats fine, let me know and i wont help you. but if you are just here to give me crap about nothing except me going against what others say, get the fxxk out of here.
simms22 said:
have you went through and installed it yet? here is the page for the android adb driver as well, it should also work http://adbdriver.com/
---------- Post added at 07:45 PM ---------- Previous post was at 07:41 PM ----------
lay off what? with helping him out? no, im not a mod, nor do i want to be a mod(i have said no to xda mod offers before). but, i will always fight against lies and untruth, no matter what, no matter who says it. i dont come here, to xda, to learn. i mostly come here to help people out. if you dont want any help, thats fine, let me know and i wont help you. but if you are just here to give me crap about nothing except me going against what others say, get the fxxk out of here.
Click to expand...
Click to collapse
Help ppl? All you do is give ppl ****. Ive seen numerous posts where you act like an a55 just cause someone needed some help or putting ppl down for using toolkits. Look i dont come here to start anything with anybody but if i see ppl unfairly treated cause they are new or dont have much experience your gonna get called out on it. As far as "getting the fxxk out of here" nah i think ill stay
chris6278 said:
Help ppl? All you do is give ppl ****. Ive seen numerous posts where you act like an a55 just cause someone needed some help or putting ppl down for using toolkits. Look i dont come here to start anything with anybody but if i see ppl unfairly treated cause they are new or dont have much experience your gonna get called out on it. As far as "getting the fxxk out of here" nah i think ill stay
Click to expand...
Click to collapse
show me one post where i acted like an ass when someone needed help.
Simms is correct, its much easy to unlock using fastboot rather than a tool kit. When I first started modding it took me >5 minutes to learn how to do this. It always works and can really help you if you mess something up using a tool kit. If the OC doesn't recognize your phone, what screen is it showing (the TWRP logo) have you tried to hold power and volume down to boot into the boot loader? If you can boot into BL then you can flash anything via fastboot and fix this problem easily.
I am unlocked and rooted. When I tried change the forced encryption is when the phone became useless. I can get it into recovery (factory) and restart bootloader, etc.
But now it justs stay on the black and white Google when your first reboot your phone.
I have downloaded all the tools. I don't know the commands or the proper order.
My computer is not reconizing my phone after the encryption attempt.
addcancercat said:
I am unlocked and rooted. When I tried change the forced encryption is when the phone became useless. I can get it into recovery (factory) and restart bootloader, etc.
But now it justs stay on the black and white Google when your first reboot your phone.
I have downloaded all the tools. I don't know the commands or the proper order.
My computer is not reconizing my phone after the encryption attempt.
Click to expand...
Click to collapse
first thing you need to do is get the driver installed, so that your device would be disabled to your computer to adb/fastboot. you are going to have to flash the factory.img through your bootloader via fastboot. or, you can fastboot oem unlock your bootloader, flash a custom recovery, and adb push/sideload a rom/gapps/supersu to your phone and flash them via your new recovery.
simms22 said:
first thing you need to do is get the driver installed, so that your device would be disabled to your computer to adb/fastboot. you are going to have to flash the factory.img through your bootloader via fastboot. or, you can fastboot oem unlock your bootloader, flash a custom recovery, and adb push/sideload a rom/gapps/supersu to your phone and flash them via your new recovery.
Click to expand...
Click to collapse
Man you wouldn't know where I might find a more detailed step by step instructions on how exactly to do this. Then I could probably do it.
I have been updating drivers, uninstalling drivers, etc.
The tiol kit was great for unlocking and rooting. Then I tried to undo the forced encryption.
Sent from my SGH-I337 using Tapatalk
addcancercat said:
Man you wouldn't know where I might find a more detailed step by step instructions on how exactly to do this. Then I could probably do it.
I have been updating drivers, uninstalling drivers, etc.
The tiol kit was great for unlocking and rooting. Then I tried to undo the forced encryption.
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
this should help you out. if you have anything to adk about it, ask there or here. good luck! http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

Any Help/Ideas would be appreciated

Ok so I have a stock, rooted, unlocked but encrypted Nexus 6. Last night it took a bad fall. The glass only cracked in one spot, however the LCD is cracked in several areas. Turning the phone on resulted in a black display. it flickers a few small bars of convoluted color, then goes black. The phone was still on and with launch everywhere I could still "Ok Google..." to do a few things.
Now, like the total idiot I am, for some damn reason I turned the phone off after getting off the phone with Asurion. And because of encryption and the screen being unresponsive (black display) I can't enter the damn screen pattern to unlock it, so I can't boot it up to drag and drop files or use adb to wipe the phone.
Does anyone have any suggestions to where I can somehow either access my files or at the very least wipe the phone? Most of my info that was on the phone is backed up to Googles servers. The are few items that aren't, that I hope I can get, but if I can't, I need to make sure are wiped. Can I enter fastboot without the pattern unlock? Or should I look into someone to repair the screen to at least get it turned on and functional to do what I need?
Thanks in advance!
Phaded said:
Can I enter fastboot without the pattern unlock?
Click to expand...
Click to collapse
If memory serves me right, you can run fastboot commands without having to enter the pattern/pin.
jj14 said:
If memory serves me right, you can run fastboot commands without having to enter the pattern/pin.
Click to expand...
Click to collapse
OK thanks. I will try that when I get home and just flash the factory image to wipe. thanks!
Hmm... from Google support pages:
If your device is running Android 5.1 or higher: Your device is protected to prevent other people from using it if it's been reset to factory settings. To ensure that it's really you doing the reset, you'll need to enter a Google username and password associated with the device after factory reset. If you don't have this information, you won't be able to finish the setup process and use the device at all after factory reset.
Does this mean even if I wipe it, the phone won't be usable for anyone?? they can't refurbish the phone because the phone will need my google info??
Eh screw it... Just gonna send it into Motorola
Phaded said:
Hmm... from Google support pages:
If your device is running Android 5.1 or higher: Your device is protected to prevent other people from using it if it's been reset to factory settings. To ensure that it's really you doing the reset, you'll need to enter a Google username and password associated with the device after factory reset. If you don't have this information, you won't be able to finish the setup process and use the device at all after factory reset.
Does this mean even if I wipe it, the phone won't be usable for anyone?? they can't refurbish the phone because the phone will need my google info??
Click to expand...
Click to collapse
yup, mean even after you wipe it, lets say 100 times, itll still ask you for your password. its security, there would be no point if you could wipe it away. but, there is a way to get rid of it, by flashing the 5.0 or 5.0.1 factory images.
simms22 said:
yup, mean even after you wipe it, lets say 100 times, itll still ask you for your password. its security, there would be no point if you could wipe it away. but, there is a way to get rid of it, by flashing the 5.0 or 5.0.1 factory images.
Click to expand...
Click to collapse
oh so if i flash an older factory image that didn't have that security feature it'll work? thanks.
Phaded said:
oh so if i flash an older factory image that didn't have that security feature it'll work? thanks.
Click to expand...
Click to collapse
yes, as long as your bootloader is unlocked. those images didn't have the security yet.
Phaded said:
they can't refurbish the phone because the phone will need my google info??
Click to expand...
Click to collapse
Hate to say this, but that's their problem You can bet that Google/Motorola will know how to get around it
---------- Post added at 01:42 PM ---------- Previous post was at 01:40 PM ----------
simms22 said:
yes, as long as your bootloader is unlocked. those images didn't have the security yet.
Click to expand...
Click to collapse
Wasn't there some issue with downgrading the bootloader causing problems? Or am I confusing with some other device?
jj14 said:
Hate to say this, but that's their problem You can bet that Google/Motorola will know how to get around it
---------- Post added at 01:42 PM ---------- Previous post was at 01:40 PM ----------
Wasn't there some issue with downgrading the bootloader causing problems? Or am I confusing with some other device?
Click to expand...
Click to collapse
It's my understanding, but I am new to the N6 so correct me if I am wrong, you can downgrade the 5.0 or 5.0.1 factory img as long as you don't downgrade to 71.05 bootloader.
byrdcfmma said:
It's my understanding, but I am new to the N6 so correct me if I am wrong, you can downgrade the 5.0 or 5.0.1 factory img as long as you don't downgrade to 71.05 bootloader.
Click to expand...
Click to collapse
that sounds about right. Just wanted to make sure op didn't flash all images in the factory image
jj14 said:
that sounds about right. Just wanted to make sure op didn't flash all images in the factory image
Click to expand...
Click to collapse
Maybe someone with more exp can give the exact process. I assume you are looking for a img with no bootloader, recovery, and radio like these http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052 but older img's
I just got my N6 yesterday, and been reading my a$$ off so I don't mess anything up. So far I have unlocked the bootloader, rooted and installed TWRP.
byrdcfmma said:
Maybe someone with more exp can give the exact process. I assume you are looking for a img with no bootloader, recovery, and radio like these http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052 but older img's
I just got my N6 yesterday, and been reading my a$$ off so I don't mess anything up. So far I have unlocked the bootloader, rooted and installed TWRP.
Click to expand...
Click to collapse
One can always go to the google developer images site (developers.google.com/android/nexus/images) and download the image they need. Unzip the downloaded file, and unzip the resulting file. In that, you'll find yet some img files, and yet another zip file that will contain the rest of the img files. Choose which one you want, and flash away
Ok so I was able to get it so the lock screen pattern is gone.
At this point I'm about to do insurance claim.
I want to pull my data (pics etc) off.
I have twrp installed and can get into recovery. Adb devices results in showing my device.
Adb/USB debugging isn't active when booted normally as I flashed new system
Tried using a tool to pull using adb, but no data gets pulled
Anyone have a method for pulling my data off? It's set to charge mode by default so it doesn't show in windows explorer.
Thanks
Sent from my Nexus 6 using XDA Free mobile app
I'm currently in the exact same predicament. Let me know how it goes.
Phaded said:
Ok so I was able to get it so the lock screen pattern is gone.
At this point I'm about to do insurance claim.
I want to pull my data (pics etc) off.
I have twrp installed and can get into recovery. Adb devices results in showing my device.
Adb/USB debugging isn't active when booted normally as I flashed new system
Tried using a tool to pull using adb, but no data gets pulled
Anyone have a method for pulling my data off? It's set to charge mode by default so it doesn't show in windows explorer.
Thanks
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Use adb pull from booted into recovery.
danarama said:
Use adb pull from booted into recovery.
Click to expand...
Click to collapse
Do you happen to know what path I would enter to pull from? I have to specify the target correct? I tried using an adb recovery tool, but when it went to /sdcard it said that path didn't exist.
I believe right now I flashed a 5.0 image (pre forced encryption?)
Sent from my Nexus 6 using XDA Free mobile app
This is the tool I tried to use:
http://forum.xda-developers.com/showthread.php?t=2339530
Sent from my Nexus 6 using XDA Free mobile app
Phaded said:
Do you happen to know what path I would enter to pull from? I have to specify the target correct? I tried using an adb recovery tool, but when it went to /sdcard it said that path didn't exist.
I believe right now I flashed a 5.0 image (pre forced encryption?)
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Is it lollipop?
You need to mount data or sdcard first.
this should work
Code:
adb shell
mount /data
exit
adb pull /data/media/0/* c:\users\phaded\desktop\mybackup\
I've made some assumptions above.
danarama said:
Is it lollipop?
You need to mount data or sdcard first.
this should work
Code:
adb shell
mount /data
exit
adb pull /data/media/0/* c:\users\phaded\desktop\mybackup\
I've made some assumptions above.
Click to expand...
Click to collapse
Yes it's lollipop, just an earlier version of it that didn't have the pattern lock (or whatever security) prompt at boot. I think 5.0.1.
I'm not rooted, does that matter for adb shell in recovery?
/data/media/0/ is my whole sd card correct? Is there a command that will show my directory in that path so I can cherry pick the folders to extract?
Sent from my Nexus 6 using XDA Free mobile app

Stock rom without root or unlock only can enter bootloader

My nexus 6 using stock rom and update to the latest version thru OTA, without root or unlock bootloader. Yesterday it suddenly reboot and only allow to boot into bootloader. Cannot select recovery or factory mode, check the bootloader log show failed to validate the boot image or recovery image.
I've read many threads and try many methods to unloock the bootloader and flash the factory image but failed.
Anyone can help to get the nexus 6 back, thanks so much.
Probably going to have to do an RMA, you can't use any of the recovery options (fastboot, custom recoveries) with a locked bootloader, that is the whole point of it being locked.
Since we're now suggesting RMA, I have to ask...
Have you tried in the bootloader screen "fastboot oem unlock"?
Maybe you have, but your problem description is really pretty vague.
scryan, not trying to tread on your toes, and I may be completely wrong (about to fall asleep) but isn't the whole point of "fastboot oem unlock" that it runs in bootloader specifically to unlock it?
dahawthorne said:
Since we're now suggesting RMA, I have to ask...
Have you tried in the bootloader screen "fastboot oem unlock"?
justMaybe you have, but your problem description is really pretty vague.
scryan, not trying to tread on your toes, and I may be completely wrong (about to fall asleep) but isn't the whole point of "fastboot oem unlock" that it runs in bootloader specifically to unlock it?
Click to expand...
Click to collapse
I am sorry as this is my 1st post here. My Nexus 6 was not rooted and even not enable "usb debug" or "oem unlock" setting.
I've already tried "fastboot oem unlock" and failed. I've also tried "fastboot flashing unloock", it said ok but restart the bootloader and it still show locked.
I've also tried the Nexus Root Tools too to unlock or flash the factory image, recovery image or boot to twrp but all failed too.
Then you have no choice but to request a RMA. To be able to unlock the bootloader so you can then flash a stock ROM, you have to enable Developer Options, then in Developer Options enable both USB Debugging and OEM Unlock.
Have you tried the hardbrick tread? Not sure if this will work with locked bootloaders. http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
Sent from my Nexus 6 using Tapatalk
---------- Post added at 09:06 PM ---------- Previous post was at 08:50 PM ----------
Have you tried fastboot reboot-recovery to enter recovery? With or without the "-", I forget the proper form. With locked bootloaders I don't think u can flash anything from recovery. Plus it may be a hardware issue not necessarily software related.
Sent from my Nexus 6 using Tapatalk
---------- Post added at 09:07 PM ---------- Previous post was at 09:06 PM ----------
But if you can enter recovery maybe you can factory reset and at least get it to boot!
Sent from my Nexus 6 using Tapatalk
---------- Post added at 10:03 PM ---------- Previous post was at 09:07 PM ----------
What version of fastboot are you using, old fastboot may not work properly.
Sent from my Nexus 6 using Tapatalk
Jnewell05 said:
Have you tried the hardbrick tread? Not sure if this will work with locked bootloaders. http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
Sent from my Nexus 6 using Tapatalk
---------- Post added at 09:06 PM ---------- Previous post was at 08:50 PM ----------
Have you tried fastboot reboot-recovery to enter recovery? With or without the "-", I forget the proper form. With locked bootloaders I don't think u can flash anything from recovery. Plus it may be a hardware issue not necessarily software related.
Sent from my Nexus 6 using Tapatalk
---------- Post added at 09:07 PM ---------- Previous post was at 09:06 PM ----------
But if you can enter recovery maybe you can factory reset and at least get it to boot!
Sent from my Nexus 6 using Tapatalk
---------- Post added at 10:03 PM ---------- Previous post was at 09:07 PM ----------
What version of fastboot are you using, old fastboot may not work properly.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thx so much for your reply, I've tried the hard-brick thread but can't install the qualcomm driver.
I plan to contact the Google see whether it can help me since I am in HK and my Nexus 6 is not directly bought from HK Google.
It really quite depress me since I do nothing with the phone, I do not flash any custom rom, do not root or unlock bootloader, just normal use it then suddenly crashed .... >_<
this exact same thing happened to my wife's phone just a month ago... and the sad thing is the phone was just bought new for only 2 months or so. never installed any custom roms, never rooted, etc. and now i wish that i did so that i could have at least turned ON that option in Developers Option to "allow OEM Unlock" and if i did, it should've been an easy fix.
i never had this kind of issue before thats why i thought there is nothing important to turn on in the Developers Option. they should've made that information more available and even point it out on the Update but they didn't which sucks.
i also tried to contact Motorola US but since im not in the US, even though the phone is bought in the US via Ebay, they weren't able to help and sent me to another Motorola site for my region. i'm trying it now and i still cant go through the site...
it's really depressing when this kind of things happen... i hope in the future there would be some kind of fix for this. i heard if we can get a signed System that we could flash into the phone then there's a chance it could work but as of now, i keep checking for information about this and hoping someone came up with something...
hope this thing won't happen to anyone else and if you got a Nexus 6, make sure to turn On "Allow OEM Unlock" on your phone.
quinceyr said:
this exact same thing happened to my wife's phone just a month ago... and the sad thing is the phone was just bought new for only 2 months or so. never installed any custom roms, never rooted, etc. and now i wish that i did so that i could have at least turned ON that option in Developers Option to "allow OEM Unlock" and if i did, it should've been an easy fix.
i never had this kind of issue before thats why i thought there is nothing important to turn on in the Developers Option. they should've made that information more available and even point it out on the Update but they didn't which sucks.
i also tried to contact Motorola US but since im not in the US, even though the phone is bought in the US via Ebay, they weren't able to help and sent me to another Motorola site for my region. i'm trying it now and i still cant go through the site...
it's really depressing when this kind of things happen... i hope in the future there would be some kind of fix for this. i heard if we can get a signed System that we could flash into the phone then there's a chance it could work but as of now, i keep checking for information about this and hoping someone came up with something...
hope this thing won't happen to anyone else and if you got a Nexus 6, make sure to turn On "Allow OEM Unlock" on your phone.
Click to expand...
Click to collapse
Hi, quinceyr, I've just tried the below thread and restore my Nexus 6 back and only draw back is updated to Android N preview version. I've tested for a while seems work fine and will keep monitor for a period.
http://forum.xda-developers.com/nexus-6/help/command-device-corrupt-update-t3362317/page2
Hope your Nexus 6 will recover back.

Categories

Resources