[Q] My Xperia V got bricked... - Sony Xperia T, TL, TX, V

Let me tell you what happened.
I tried to relock my Xperia V (unlocked BL) with latest version of flashtool (v.0.9.16.1) and it seemed successful.
After I unplugged the cable and rebooted my phone (It had a normally working stock FW of 9.2.A.1.120), it stucked right after the SONY logo for some minutes and powered off automatically
And now every time I try to power it on, it does actually the same thing:
1. shows the SONY logo
2. shows this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and stays for about 5-10 minutes.
3. becomes blank screen and does not try to boot again.
As it could be set to Fastboot Mode and Flash Mode, I also tried to solve it but of no use. Here are my attempts:
1. Using PC Companion or SONY Update Service to repair both results in failure
2. Using Flashtool to flash FTFs gets following error messages
ERROR - ERR_SEVERITY="MAJOR";ERR_CODE="0026";ERR_DYNAMIC="08 : TA flush failed";
3. Also tried to re-unlock the relocked BL...
On the first time of trying after a reboot, the fastboot.exe says: FAILED (remote: oem unlock failed!)
and on the following attempts it keeps telling me: FAILED (remote: Phone is already unlocked!)
(but actually it's still locked)
Now I could neither flash anything into it, nor unlock the BL...
Totally confused about this situation. Would relocking BL brick a phone? Is there any solution to this?
Thank you!

char.c said:
2. Using Flashtool to flash FTFs gets following error messages
ERROR - ERR_SEVERITY="MAJOR";ERR_CODE="0026";ERR_DYNAMIC="08 : TA flush failed";
Click to expand...
Click to collapse
Open up Flashtool, select the FTF you want to flash and check TA inside the "Exclude" box.
Then try to flash...

istux said:
Open up Flashtool, select the FTF you want to flash and check TA inside the "Exclude" box.
Then try to flash...
Click to expand...
Click to collapse
Thank you for replying.
But I've already tried that... same error after flashed loader.sin. I couldn't avoid loader.sin (excluded everything and wiped no data at all, there's still loader.sin left, which leads to the same failure)

char.c said:
Thank you for replying.
But I've already tried that... same error after flashed loader.sin. I couldn't avoid loader.sin (excluded everything and wiped no data at all, there's still loader.sin left, which leads to the same failure)
Click to expand...
Click to collapse
You said you tried to re-lock again, but have you tried to re-unlock again and flash?
I guess the way you relocked just messed up something... all those errors are about a wrong kernel usually...
Anyway your phone is not hard-bricked, but just soft-bricked... and this problem seems to be new here

istux said:
You said you tried to re-lock again, but have you tried to re-unlock again and flash?
I guess the way you relocked just messed up something... all those errors are about a wrong kernel usually...
Anyway your phone is not hard-bricked, but just soft-bricked... and this problem seems to be new here
Click to expand...
Click to collapse
Yes, tried to re-unlock, but failed......:crying:
char.c said:
3. Also tried to re-unlock the relocked BL...
On the first time of trying after a reboot, the fastboot.exe says: FAILED (remote: oem unlock failed!)
and on the following attempts it keeps telling me: FAILED (remote: Phone is already unlocked!)
(but actually it's still locked)
Click to expand...
Click to collapse

istux said:
You said you tried to re-lock again, but have you tried to re-unlock again and flash?
I guess the way you relocked just messed up something... all those errors are about a wrong kernel usually...
Anyway your phone is not hard-bricked, but just soft-bricked... and this problem seems to be new here
Click to expand...
Click to collapse
I just followed a guide about using Flashtool to relock BL...
And other people who also used Flashtool to relock their phones did not face the same problem... That's why I'm totally confused. I cannot figure out what went wrong during the relock process.

char.c said:
I just followed a guide about using Flashtool to relock BL...
And other people who also used Flashtool to relock their phones did not face the same problem... That's why I'm totally confused. I cannot figure out what went wrong during the relock process.
Click to expand...
Click to collapse
The best way to relock is restoring a TA backup, that has to be done before unlocking the first time.
If you didn't backup TA, then you lost your DRM keys forever.
So you relocked using Flashtool. Right?
What guide did you follow? Give me the link, please.
I hope you didn't flash BLRelock for X10

istux said:
The best way to relock is restoring a TA backup, that has to be done before unlocking the first time.
If you didn't backup TA, then you lost your DRM keys forever.
So you relocked using Flashtool. Right?
What guide did you follow? Give me the link, please.
I hope you didn't flash BLRelock for X10
Click to expand...
Click to collapse
I didn't know anything about TA backup when I unlocked my phone.
So I'm not able to relock like that.
Here's the guide I followed. I didn't flashed that X10 relock TFT.
http://forum.xda-developers.com/showthread.php?p=45653511#post45653511

char.c said:
I didn't know anything about TA backup when I unlocked my phone.
So I'm not able to relock like that.
Here's the guide I followed. I didn't flashed that X10 relock TFT.
http://forum.xda-developers.com/showthread.php?p=45653511#post45653511
Click to expand...
Click to collapse
I know you didn't make a TA backup.
With your next xperia device, remember to do it
The guide you followed is right and comes from a very reliable developer.
According to all steps you did, I think you have nothing more to try... you did all what has to be done in this case.
Try to download another FTF, maybe yours is corrupted. But I don't think so actually (because also SONY Update Service repair didn't work).
I mean, your device behaviour is weird and no-sense.
Something is broken if you can't work with kernel partition.
Maybe your motherboard is fried
When we play with an unlocked bootloader, this can happen sometimes.
The problem is that your warranty is lost if sony repair center realizes that it was unlocked.
Sorry if I can't help you out further. :crying:
Good luck anyways

istux said:
I know you didn't make a TA backup.
With your next xperia device, remember to do it
The guide you followed is right and comes from a very reliable developer.
According to all steps you did, I think you have nothing more to try... you did all what has to be done in this case.
Try to download another FTF, maybe yours is corrupted. But I don't think so actually (because also SONY Update Service repair didn't work).
I mean, your device behaviour is weird and no-sense.
Something is broken if you can't work with kernel piartition.
Maybe your motherboard is fried
When we play with an unlocked bootloader, this can happen sometimes.
The problem is that your warranty is lost if sony repair center realizes that it was unlocked.
Sorry if I can't help you out further. :crying:
Good luck anyways
Click to expand...
Click to collapse
Well, thanks anyway.
Having tried for over 10 hrs to repair it and failed, I'll send it to repair tomorrow. Hope the fee won't be too high
At least no higher than a new phone

Related

[Q] My TX screen upside down!!

I tried to fix it by flash the orginal TFT with flashtool but it's still can't not work...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is the touch firamware problem?
Anybody know how can I fix it?
Thanks for help
Repair using pccompanion
Sent from my LT30p using xda premium
gregbradley said:
Repair using pccompanion
Sent from my LT30p using xda premium
Click to expand...
Click to collapse
When I use the PPC to repair it will appear
problem
"The phone include the software that can't modify and update"
detail:
"The update service of Sony is fail (error:2003)"
I tried to translate...hope my english is ok...
My phone has no root and locked...
skylovely2005 said:
When I use the PPC to repair it will appear
problem
"The phone include the software that can't modify and update"
detail:
"The update service of Sony is fail (error:2003)"
I tried to translate...hope my english is ok...
My phone has no root and locked...
Click to expand...
Click to collapse
goto phone and dial
*#*#7378423#*#* and goto service info / configuration and tell me what it says in the last line under "bootloader status"
gregbradley said:
goto phone and dial
*#*#7378423#*#* and goto service info / configuration and tell me what it says in the last line under "bootloader status"
Click to expand...
Click to collapse
It's look like this
You have unlocked your bootloader (Even though you say you haven't) that's why pccompanion wont work
Flash the relock ftf for your phone then repair using pccompanion. (Find the FTF file here)
Or find the correct ftf for your phone and flash it in flashtool.
PS (Can you tell me the link for the ftf you tried to flash, this problem normally happens when people flash a T ftf on a TX or vice versa)
gregbradley said:
You have unlocked your bootloader (Even though you say you haven't) that's why pccompanion wont work
Flash the relock ftf for your phone then repair using pccompanion. (Find the FTF file here)
Or find the correct ftf for your phone and flash it in flashtool.
PS (Can you tell me the link for the ftf you tried to flash, this problem normally happens when people flash a T ftf on a TX or vice versa)
Click to expand...
Click to collapse
My TFT is download in another forum...
and the name is "LT29i_9.1.B.1.67_1266-5825-R2I.ftf",
I don't know when do I unlocked my bootloader= =..
but I have download the relock ftf ,
let me try PPC =)
thanks you
You unlocked your bootloader when you went to the sony website and followed the instructions on how to unlock our bootloader.
Unless, you got the phone second hand then you must have done it, because they are not sold with unlocked bootloaders.
Let me know if it works when you have repaired with pccompanion
gregbradley said:
You unlocked your bootloader when you went to the sony website and followed the instructions on how to unlock our bootloader.
Unless, you got the phone second hand then you must have done it, because they are not sold with unlocked bootloaders.
Let me know if it works when you have repaired with pccompanion
Click to expand...
Click to collapse
It's still have same problem..
The screen still upside down ><
I have flash this rom this morning
http://forum.xda-developers.com/showthread.php?t=2407313
and try to use this patch
http://forum.xda-developers.com/showthread.php?t=2268401
then the screen is upside down...
I tried everything I can do and then no ussful =(
skylovely2005 said:
It's still have same problem..
The screen still upside down ><
Click to expand...
Click to collapse
goto phone and dial
*#*#7378432#*#* and goto service info / model info and tell me what it says there
gregbradley said:
goto phone and dial
*#*#7378432#*#* and goto service info / model info and tell me what it says there
Click to expand...
Click to collapse
I can't not get in to engineer mode= =...
Let me tried later...QQ
OK.
I suggest you redownload a TX FTF (Find one in the all in one thread) and flash it again in flashtool making sure you wipe everything.
gregbradley said:
OK.
I suggest you redownload a TX FTF (Find one in the all in one thread) and flash it again in flashtool making sure you wipe everything.
Click to expand...
Click to collapse
Model info:
LT29i
There was a problem after applying this patch. Helped only a replacement touchscreen. Flashing did not help.
nnmka said:
There was a problem after applying this patch. Helped only a replacement touchscreen. Flashing did not help.
Click to expand...
Click to collapse
How can I replace my [email protected]@?
In your case, it is better to contact the service center. I no recovery path did not help. Only replacement touchscreen.
nnmka said:
In your case, it is better to contact the service center. I no recovery path did not help. Only replacement touchscreen.
Click to expand...
Click to collapse
Oh no...
It's so sad...
So ti's a hardware's problem...
Thanks for your help ><
This is not a hardware problem and you have not flashed a "patch"
Find a TX FTF from the all in one thread and flash it. Make sure you exclude nothing and wipe everything.
Plus going to service centre is no good because you have voided your warrenty by unlocking the bootloader.
gregbradley said:
This is not a hardware problem and you have not flashed a "patch"
Find a TX FTF from the all in one thread and flash it. Make sure you exclude nothing and wipe everything.
Plus going to service centre is no good because you have voided your warrenty by unlocking the bootloader.
Click to expand...
Click to collapse
I don't flashed the patch anymore when I flashed the TX FTF,
I will try again with this one http://forum.xda-developers.com/showthread.php?p=39842542#post39842542
Thanks for your patient =)
Hope this time can resolve.
p.s If I unlock again they will know I have been unlocked my [email protected]@?
That should be fine,.
They know you have unlocked because
1) You gave them your IMEI number when you unlocked.
2) You have lost your DRM keys.
3) You have altered your TA partition.
Relocking your bootloader does not fix any of these things

[Q] So tired.. I will give up with these alien words.

Guys I have been looking through tutorials for rooting etc. I know I am the 23473047230th noob asking around and believe me the last option for me was to post here. I have made the unlocked bootloader (yaaay! :victory: ), and then as I am on 4.3 - 12.1.A.1.201 I said oh wait! I read on various comments that the Wi-Fi is not working after flashing the kernel into 12.1.A.0.266 so I freaked out and did not proceed.
My question comes. Flashing a kernel into 12.1.A.0.266 is just downgrade so as to root it? I am reading this guide which has not detailed info (for noobs)
[ how to flash this kernel ] (via fastboot)
download the kernel image
save the SP_DooMLoRD_AdvStkKernel_FW-XXX_vXX.elf to the folder containing fastboot binary
flash the SP_DooMLoRD_AdvStkKernel_FW-XXX_vXX.elf using fastboot:
Click to expand...
Click to collapse
I have downloaded this file "SP_DooMLoRD_AdvStkKernel_FW-266_v01.elf" and got a Flashtool. On a video guide it says to move the file into D:\Flashtool\firmwares is it right? Do I need anything else? Should I proceed? After this I will proceed with this root guide
Rooting Instructions
[ how to root ]
once you have flashed the kernel from the 1st post
download the latest SuperSU update.zip from: http://download.chainfire.eu/supersu
save it on sdcard of device
reboot into recovery
flash the supersu update.zip
reboot from recovery into OS
you should now get proper root access!
Click to expand...
Click to collapse
... and then I will throw a heavy metal party to relax and stress out of my nerves!
IreneGR said:
Guys I have been looking through tutorials for rooting etc. I know I am the 23473047230th noob asking around and believe me the last option for me was to post here. I have made the unlocked bootloader (yaaay! :victory: ), and then as I am on 4.3 - 12.1.A.1.201 I said oh wait! I read on various comments that the Wi-Fi is not working after flashing the kernel into 12.1.A.0.266 so I freaked out and did not proceed.
My question comes. Flashing a kernel into 12.1.A.0.266 is just downgrade so as to root it? I am reading this guide which has not detailed info (for noobs)
I have downloaded this file "SP_DooMLoRD_AdvStkKernel_FW-266_v01.elf" and got a Flashtool. On a video guide it says to move the file into D:\Flashtool\firmwares is it right? Do I need anything else? Should I proceed? After this I will proceed with this root guide
... and then I will throw a heavy metal party to relax and stress out of my nerves!
Click to expand...
Click to collapse
Contact me through skype and I'll help you
"UltraWelfare"
UltraWelfare said:
Contact me through skype and I'll help you
"UltraWelfare"
Click to expand...
Click to collapse
I would like to, but I am deaf and can't hear you.. :/ I will add you anyway!!!
Do you know how to check if my TA partition is safe?
EDIT: I run TrackID as I found on your forums and it is working ... I guess I am so lucky lol.
Well I am thinking of relocking the bootloader, should I make a TA partition?
OK I will try and explain this as simply as possible.
IreneGR said:
I have made the unlocked bootloader (yaaay! :victory: ),
Click to expand...
Click to collapse
This is good it will simplify the root procedure. On a side note did you backup the TA partition before doing this?
and then as I am on 4.3 - 12.1.A.1.201 I said oh wait! I read on various comments that the Wi-Fi is not working after flashing the kernel into 12.1.A.0.266 so I freaked out and did not proceed.
Click to expand...
Click to collapse
It doesn't matter if the WiFi stops working as it will start working again when you reflash the stock 201 kernel.
My question comes. Flashing a kernel into 12.1.A.0.266 is just downgrade so as to root it? I am reading this guide which has not detailed info (for noobs)
Click to expand...
Click to collapse
No this is not a downgrade to root you are flashing doom kernel which will allow root where the stock kernel will not.
I have downloaded this file "SP_DooMLoRD_AdvStkKernel_FW-266_v01.elf" and got a Flashtool. On a video guide it says to move the file into D:\Flashtool\firmwares is it right? Do I need anything else? Should I proceed? After this I will proceed with this root guide
Click to expand...
Click to collapse
That it correct after you have finished this root guide you can download and flash the .201stock kernel through flashtool that will clear up any WiFi issues you may have.
Hope this helps clear things up a bit
Sent from my C5303 using xda devlopers app
After a further further research (got almost a headache) I did until unlocked bootloader. I talked with a guy here and he suggested me to relock the bootloader and to do it in other way.
Well I didn't TA partition but TrackID is working and the IMEI is there... I cannot explain it... Do you know any other way to check if they DMR keys are okey?
Also do you know in case I relock my bootloader should I use the TA partition part?
IreneGR said:
After a further further research (got almost a headache) I did until unlocked bootloader. I talked with a guy here and he suggested me to relock the bootloader and to do it in other way.
Well I didn't TA partition but TrackID is working and the IMEI is there... I cannot explain it... Do you know any other way to check if they DMR keys are okey?
Also do you know in case I relock my bootloader should I use the TA partition part?
Click to expand...
Click to collapse
If you already unlocked your bootloader and didnt backup your TA-partition, your TA-partition will be lost forever .
I believe you can lock your bootloader again but this is without DRM-keys (I think).
And I believe TrackID will work even with unlocked bootloader and without DRM-keys. Im using TrackID on CM11 so yeah .
Just type *#*#7378423#*#* for checking bootloader status.
Th3Duck said:
If you already unlocked your bootloader and didnt backup your TA-partition, your TA-partition will be lost forever .
I believe you can lock your bootloader again but this is without DRM-keys (I think).
And I believe TrackID will work even with unlocked bootloader and without DRM-keys. Im using TrackID on CM11 so yeah .
Just type *#*#7378423#*#* for checking bootloader status.
Click to expand...
Click to collapse
I see, no problem then It's ok I will survive! haha! Yes its unlocked. I am checking this video on how to relock it and I will proceed with another guide.
Would you like to exchange Skype and help me through this?
EDIT: I am trying to relock it but it stacks here why?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
IreneGR said:
I see, no problem then It's ok I will survive! haha! Yes its unlocked. I am checking this video on how to relock it and I will proceed with another guide.
Would you like to exchange Skype and help me through this?
Click to expand...
Click to collapse
Mmmm for relocking your bootloader I thought you dont need extra files anymore because in the newest flashtool there is a button for that (thought I read that somewhere, not sure). Still your DRM keys will be lost, because you dont have backup of your TA-partition. So relocking bootloader isnt that usefull for you. Just keep it unlocked
For your previous post (the pictures) you put your phone in fastboot mode instead of flashmode .
My life is ruined now lol. I have this problem "Stuck on SONY LOGO" so I am downloading a greek stock .. hope it fix it... (it doesnt matter the version number right?)

[Q] Can't figure anything out

So I just got the Google Play Edition and I can't seem to figure any tutorial thread out on how to unlock the bootloader then root my phone, then install a custom recovery, then install a rom :/ I need some help. So currently, I am at the htcdev part to unlock bootloader using this tutorial. When I get to step 11 it says to skip to step 8 which I can not do on the page (Guessing the guide is outdated?). So I go ahead and do step 5-7 and when I type "fastboot oem get_identifier_token" on step 5 it just stays stuck on "waiting for device" on the CMD prompt. What am I doing wrong?
PS. which I click fastboot as instructed on step 2 of htcdev it just send me back to the screen before.
EvoTheBoy said:
So I just got the Google Play Edition and I can't seem to figure any tutorial thread out on how to unlock the bootloader then root my phone, then install a custom recovery, then install a rom :/ I need some help. So currently, I am at the htcdev part to unlock bootloader using this tutorial. When I get to step 11 it says to skip to step 8 which I can not do on the page (Guessing the guide is outdated?). So I go ahead and do step 5-7 and when I type "fastboot oem get_identifier_token" on step 5 it just stays stuck on "waiting for device" on the CMD prompt. What am I doing wrong?
PS. which I click fastboot as instructed on step 2 of htcdev it just send me back to the screen before.
Click to expand...
Click to collapse
Stuck waiting for device mean your drivers are not installed preoperly, download HTC Sync manager install it and then remove HTC sync, you will see the driver package above it, leave that alone.
Also, your phone must be in the bootloader when trying to get ID token, not booted up. (just in case)
Instructions to unlock the bootloader are at HTCDev whilst your trying to actually unlock the bootloader, you will need to register: http://www.htcdev.com/bootloader unlocking is the easy part.
Seanie280672 said:
Stuck waiting for device mean your drivers are not installed preoperly, download HTC Sync manager install it and then remove HTC sync, you will see the driver package above it, leave that alone.
Also, your phone must be in the bootloader when trying to get ID token, not booted up. (just in case)
Instructions to unlock the bootloader are at HTCDev whilst your trying to actually unlock the bootloader, you will need to register: http://www.htcdev.com/bootloader unlocking is the easy part.
Click to expand...
Click to collapse
Thank you for the reply! I got as far as inputting "fastboot flash unlocktoken Unlock_code.bin" into the cmd prompt which says it was successful but doesn't show nor do anything on my phone like it says it should. Any ideas on how to fix that?
EvoTheBoy said:
Thank you for the reply! I got as far as inputting "fastboot flash unlocktoken Unlock_code.bin" into the cmd prompt which says it was successful but doesn't show nor do anything on my phone like it says it should. Any ideas on how to fix that?
Click to expand...
Click to collapse
Really sorry I didn't read your first post properly, you have a gpe device, different kettle of fish, the HTC dev way doesn't work for gpe, try this instead.
http://www.ibtimes.co.uk/htc-one-google-play-edition-how-unlock-bootloader-root-install-twrp-1429968
For the Google Play Edition just use fastbot oem unlock and you're done
However, bear in mind that you won't be able to use Sense-based ROMs as the partitions are different. You're limited to AOSP/CM-based ROMs (unless you can convert to a Sense M7, which I assume so as they're technically the same device)
Seanie280672 said:
Really sorry I didn't read your first post properly, you have a gpe device, different kettle of fish, the HTC dev way doesn't work for gpe, try this instead.
http://www.ibtimes.co.uk/htc-one-google-play-edition-how-unlock-bootloader-root-install-twrp-1429968
Click to expand...
Click to collapse
EddyOS said:
For the Google Play Edition just use fastbot oem unlock and you're done
However, bear in mind that you won't be able to use Sense-based ROMs as the partitions are different. You're limited to AOSP/CM-based ROMs (unless you can convert to a Sense M7, which I assume so as they're technically the same device)
Click to expand...
Click to collapse
I keep getting this error :/ Idk if this helps but it says s-on and hboot is 1.54 and my OS is 5.11.1700.3
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That's really strange, I've never seen that before. I'm gonna tag @graffixnyc and see if he chimes in, but he is busy these days but it's almost like it can't load up the screen which gives you the option to unlock the bootloader (where you choose yes or no)
EddyOS said:
That's really strange, I've never seen that before. I'm gonna tag @graffixnyc and see if he chimes in, but he is busy these days but it's almost like it can't load up the screen which gives you the option to unlock the bootloader (where you choose yes or no)
Click to expand...
Click to collapse
It is weird. I googled it and came about people saying to downgrade (Which I have 0 knowledge of when it comes to HTC devices.. coming from LG as my device with experience). Idk. Thanks for the help hopefully someone can help me out about this.
The whole point of the GPe phones is that they're easy to unlock, like a Nexus, so it should just unlock with that command. The only thing I can think of is you're using outdated fastboot files so perhaps looks into updating them but failing that I'm at a loss
EddyOS said:
The whole point of the GPe phones is that they're easy to unlock, like a Nexus, so it should just unlock with that command. The only thing I can think of is you're using outdated fastboot files so perhaps looks into updating them but failing that I'm at a loss
Click to expand...
Click to collapse
Guess that isn't the problem :/ I triple checked to make sure I had the right fastboot and I kept getting the same error.
EddyOS said:
That's really strange, I've never seen that before. I'm gonna tag @graffixnyc and see if he chimes in, but he is busy these days but it's almost like it can't load up the screen which gives you the option to unlock the bootloader (where you choose yes or no)
Click to expand...
Click to collapse
I've never seen that.. It's very odd.
graffixnyc said:
I've never seen that.. It's very odd.
Click to expand...
Click to collapse
I read online about it and saw some say to call google and they could help fix the problem cause it is a problem within the actual device. I called them and they didn't help lol. Anyways, my device is still under warranty and has the purple camera tint problem so I will try to send it in and hopefully get a new model back.
OT: if anyone has had this error before please say how you fixed it thanks
UPDATE: After some googling I found out that after 4.4.2 fastboot oem unlock does not work anymore with this devices (I am on 5.0.1)

Can you plz tell me if I doing the right steps?

Hi,
How are you?
I want to do "back to rom stock" + re-lock the bl.
Before the procedure I want to be sure that I'm doing the right steps - so, can you please approve that?
1. Downloading the recent "shamu" image (6.0.1 (MOB30W) and Extract directly to Platform-tools folder these:
- shamu-XXXXX.tgz
- shamu-XXXXX.tar
2. Open the CMD from Platform-tools folder and start typing 1 by 1:
- fastboot flash system system.img
- fastboot flash boot boot.img
- fastboot flash recovery recovery.img
- fastboot flash cache cache.img
- fastboot flash userdata userdata.img
- fastboot reboot
Is this process completely bring the N6 back to Google rom stock + re-lock the bootloader?
Thanks for your time & help!
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
And don't lock you bootloader, or at least leave it unlockable, unless you want to sell it. Google can brick it with an OTA.
Hi @istperson
1) You guess it correctly - I do want to sell it.
(It would be better just to relock and thats it?)
Why would Google's OTA will brick it while it exactly back to stock without root?
2) Can you plz review my 1st message here to tell me if everything is correct?
3) For some reasson (maybe Win10 upgrade) the drivers are not working anymore('fastboot devices' dose not showing anything)
Setting the driver is one of those things that could make me crazy...:cyclops:
Is there a tool that just do everthing by itself? (i'm not talking about flash tools that guides you).
Thanks a lot!
shabydog said:
Hi @istperson
1) You guess it correctly - I do want to sell it.
(It would be better just to relock and thats it?)
Why would Google's OTA will brick it while it exactly back to stock without root?
2) Can you plz review my 1st message here to tell me if everything is correct?
3) For some reasson (maybe Win10 upgrade) the drivers are not working anymore('fastboot devices' dose not showing anything)
Setting the driver is one of those things that could make me crazy...:cyclops:
Is there a tool that just do everthing by itself? (i'm not talking about flash tools that guides you).
Thanks a lot!
Click to expand...
Click to collapse
No, your steps are not correct. Follow the steps in the link that was provided in post 2.
Any tool would still have to have the drivers properly setup and adb working. The nexus is one of the easiest devices to restore to stock. But there is no magic wand.
shabydog said:
Why would Google's OTA will brick it while it exactly back to stock without root?
Click to expand...
Click to collapse
If you want to lock it, then leave it as a last step when everything else worked. And the phone is completely back to stock, and booted up okay, and everything.
And Google made a couple of ugly mistakes in OTA-s, and the phones bootlooped. And yes they were not rooted, they were completely stock, because otherwise the OTA wouldn't have installed.
@ktmom
I posted this AFTER I MADE A RESEARCH all over...So please believe me that I need help (maybe bc's it's harder for me with much of information).
Please try to do your best to help me here bc's I been lost (and I know a bit or more in this)
Thanks.
@istperson
So, if i completely proceed with the all the necessary commands it will also relock the BL.
Do you think that it's better to NOT relock it (but if these commands doing that...)?
Thanks!
shabydog said:
@istperson
So, if i completely proceed with the all the necessary commands it will also relock the BL.
Do you think that it's better to NOT relock it (but if these commands doing that...)?
Thanks!
Click to expand...
Click to collapse
The bootloader is locked with the "fastboot oem lock" command.
If you're selling it then put it back to the original factory state. Without WiFi and sim card it will not receive updates. So let the new owner decide it he or she will unlock it or not.
Just don't lock it before you checked it boots.
Sent to another responce below
The updated replay bellow (found a method of "flash-all" script)
Hope to get an answer to this...
1) Found this (attached iamge), think it solve my question, right?
2) Drivers: I made a test - booted the n6 to BL and typed from the folder of the platform-tools: adb devices which gave me combination of numbers+letters ending with 'device'.
Guess that mean that the drivers are setted?
3) Heard something about that it's NOT recommanded to flash the rom stock bc's if the user doing an OTA it will brick the device?
So it better not proceed the 'fastboot oem lock'?
Anyone knows about it?
Thank you!
adb works in normally booted phone and in recovery. In bootloader mode you use fastboot.
Stock images won't brick your device, but an OTA might. Don't use OTAs, flash manually the updates. But you said you want to sell the phone, then flash stock, lock it, and sell it.
istperson said:
adb works in normally booted phone and in recovery. In bootloader mode you use fastboot.
Stock images won't brick your device, but an OTA might. Don't use OTAs, flash manually the updates. But you said you want to sell the phone, then flash stock, lock it, and sell it.
Click to expand...
Click to collapse
I followed by this tut )just without the last stage of unlocking bootloader:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You do realize that if you followed the directions in post #2 given to you 6 days ago, you would have been done? I'm certainly not going to rehash here what's been perfectly described in that thread.
Hi,
Eventually I used the Nexus Toolkit and Flashed +Unroot sucssesfuly.
Can you plz reminde me - I did not got that: Should I leave the BL unlocked to avoid BRICK or opposite?
Thanks!
You want to keep it or sell it? If you want to sell it then lock it.

General Progress/How to in modding(rooting, recoveries,etc)

Hi!
As you may know Honor is pretty restricted in modding.
I AM NOT RESPONSIBLE FOR ERRORS/BRICKED DEVICES'
THIS JUST GIVES AN IDEA ON WHAT TO DO AND IF YOU SHOULD BUY( I don't recommend for modding)
EDIT: IT SEEMS LIKE WE CANT UNLOCK THE BL
There are no recoveries yet
So we need boot.img to root with magisk
But Honor/Other websites does not provide firmware
So we need to dump firmware(which I have not done yet) to get boot.img using mtk client or unlocktool (idk if unlocktool is legit)
Then patch boot.img and flash
#YetAnotherPerson said:
Hi!
As you may know Honor is pretty restricted in modding.
I AM NOT RESPONSIBLE FOR ERRORS/BRICKED DEVICES'
THIS JUST GIVES AN IDEA ON WHAT TO DO AND IF YOU SHOULD BUY( I don't recommend for modding)
There are no recoveries yet
So we need boot.img to root with magisk
But Honor/Other websites does not provide firmware
So we need to dump firmware(which I have not done yet) to get boot.img using mtk client or unlocktool (idk if unlocktool is legit)
Then patch boot.img and flash
Click to expand...
Click to collapse
Hi! Thanks for requesting this page!
For anyone considering buying this phone, just like OP said, DON'T buy if you want to MOD it in any way!
Also, if anyone has any information on this phone, like the firmware, exploits, etc. PLEASE share it since this device is not even that known in XDA.
Sad update, I backed up my Linux computer to install windows and use many apps to retrieve stock firmware for rooting and when device gets bricked, but no success, and I installed Linux again. I did not dual boot because of storage issues
Our hope is not fully lost.
We could flash a rooted GSI.
But I just don't want to risk it as there is no way to return back to the stock firmware if something goes wrong or some features don't work(that's sometimes how GSI's are
#YetAnotherPerson said:
Our hope is not fully lost.
We could flash a rooted GSI.
But I just don't want to risk it as there is no way to return back to the stock firmware if something goes wrong or some features don't work(that's sometimes how GSI's are
Click to expand...
Click to collapse
But wouldn't we need to at least unlock the bootloader to flash anything?
JoeBro19 said:
But wouldn't we need to at least unlock the bootloader to flash anything
Click to expand...
Click to collapse
There is a bootloader unlock option in settings, developer options
#YetAnotherPerson said:
There is a bootloader unlock option in settings, developer options
Click to expand...
Click to collapse
That's only an option to allow the device to be unlocked, but it doesn't unlock it per se. That's done in fastboot mode or similar where you enter a code to unlock it, but Huawei/Honor stopped giving those codes years ago, that's why it's so difficult to do anything to these phones...
JoeBro19 said:
That's only an option to allow the device to be unlocked, but it doesn't unlock it per se. That's done in fastboot mode or similar where you enter a code to unlock it, but Huawei/Honor stopped giving those codes years ago, that's why it's so difficult to do anything to these phones...
Click to expand...
Click to collapse
Hi!
Do you know any way to check if the bootloader is unlocked other than the phone and fastboot method(those don't work for me). I think I did unlock the bootloader, here is what I did:
1. I typed "fastboot flashing unlock"
2. THAT BRICKED MY PHONE
3. I booted into recovery and did a factory reset
4. Did my usual setup again
5. I just went into settings(developer options) and the OEM unlock toggle was enabled without me touching it!
#YetAnotherPerson said:
Hi!
Do you know any way to check if the bootloader is unlocked other than the phone and fastboot method(those don't work for me). I think I did unlock the bootloader, here is what I did:
1. I typed "fastboot flashing unlock"
2. THAT BRICKED MY PHONE
3. I booted into recovery and did a factory reset
4. Did my usual setup again
5. I just went into settings(developer options) and the OEM unlock toggle was enabled without me touching it!
Click to expand...
Click to collapse
You can check by entering fastboot/bootloader mode and it'll say if the phone (bootloader) is locked or unlocked.
You can enter the bootloader by using adb and entering "adb reboot bootloader" and after you get restarted into the bootloader it'll tell you the status on the bottom of the screen.
I have that OEM unlock toggled on and as it still says "Phone Locked" in the bootloader, just as I said that toggling that option doesn't actually unlock it.
JoeBro19 said:
You can check by entering fastboot/bootloader mode and it'll say if the phone (bootloader) is locked or unlocked.
You can enter the bootloader by using adb and entering "adb reboot bootloader" and after you get restarted into the bootloader it'll tell you the status on the bottom of the screen.
I have that OEM unlock toggled on and as it still says "Phone Locked" in the bootloader, just as I said that toggling that option doesn't actually unlock it.
Click to expand...
Click to collapse
Thanks!
While I did not make any progress, atleast I found out I wasted my time "unlocking" the BL and still nothing happened. Just to confirm that the phone locked thing does change when BL in unlocked, I checked a yt video on someone flashing a GSI on an older honor device and it does say "phone unlocked" for them.
Let me explain a bit more on what happened on the BL unlock attempt:
1.I did fastboot flashing unlock in adb which should unlock the BL
2.It put me in a menu which had an option to unlock the bootloader and it did say it will void warranty
3. Then it said it was a sucess and then went into another menu asking what to do next (fastboot mode,reboot,and something else) but it glitched and clicking hw buttons did nothing so I rebooted and the device was in a bootloop so I had to reset the device using the recovery
4. In fastboot mode, it still says phone locked
In short: There is a bug preventing BL unlock. I am not sure if Honor devices still need a code to unlock the BL since you said they stopped providing them
#YetAnotherPerson said:
Thanks!
While I did not make any progress, atleast I found out I wasted my time "unlocking" the BL and still nothing happened. Just to confirm that the phone locked thing does change when BL in unlocked, I checked a yt video on someone flashing a GSI on an older honor device and it does say "phone unlocked" for them.
Let me explain a bit more on what happened on the BL unlock attempt:
1.I did fastboot flashing unlock in adb which should unlock the BL
2.It put me in a menu which had an option to unlock the bootloader and it did say it will void warranty
3. Then it said it was a sucess and then went into another menu asking what to do next (fastboot mode,reboot,and something else) but it glitched and clicking hw buttons did nothing so I rebooted and the device was in a bootloop so I had to reset the device using the recovery
4. In fastboot mode, it still says phone locked
In short: There is a bug preventing BL unlock. I am not sure if Honor devices still need a code to unlock the BL since you said they stopped providing them
Click to expand...
Click to collapse
Being an Honor device, it most likely needs a code to unlock it. So I doubt we'll be able to do anything with this phone.
I could try and do a backup before trying what you did to see if it was a just a bug on your phone or if in fact it can't be done at all, which honestly is the most probable case.
I'll try later and let you know if anything happens.
JoeBro19 said:
Being an Honor device, it most likely needs a code to unlock it. So I doubt we'll be able to do anything with this phone.
I could try and do a backup before trying what you did to see if it was a just a bug on your phone or if in fact it can't be done at all, which honestly is the most probable case.
I'll try later and let you know if anything happens.
Click to expand...
Click to collapse
Ok, but
JoeBro19 said:
Being an Honor device, it most likely needs a code to unlock it. So I doubt we'll be able to do anything with this phone.
I could try and do a backup before trying what you did to see if it was a just a bug on your phone or if in fact it can't be done at all, which honestly is the most probable case.
I'll try later and let you know if anything happens.
Click to expand...
Click to collapse
Ok, but I'll give another warning: It's risky and may brick your device like mine and a factory reset from the recovery may be required. I am not respondible if something happens.
I did contact honor customer support but no reply yet
#YetAnotherPerson said:
Ok, but
Ok, but I'll give another warning: It's risky and may brick your device like mine and a factory reset from the recovery may be required. I am not respondible if something happens.
I did contact honor customer support but no reply yet
Click to expand...
Click to collapse
I doubt they'll anything other than "we don't provide those codes anymore"
And yeah I decided to try it anyway and it happened exactly the same as your case. I had to factory reset it to exit the boot loop. Fortunately, I did a backup just before trying it so I was able to restore it and not lose anything; but yeah, things seem to have come to a standstill.
JoeBro19 said:
I doubt they'll anything other than "we don't provide those codes anymore"
And yeah I decided to try it anyway and it happened exactly the same as your case. I had to factory reset it to exit the boot loop. Fortunately, I did a backup just before trying it so I was able to restore it and not lose anything; but yeah, things seem to have come to a standstill.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
#YetAnotherPerson said:
View attachment 5902653
Click to expand...
Click to collapse
Just as I thought.... damn this companies...
So, unless some miracle happens and someone discovers an exploit on the processor or something that allows us to decipher the unlock code, there is absolutely nothing than we can do...
You can only unlock the bootloader on the new Honor at the Honor office. But this is only possible if the Honor employee is your friend.
volkodav1975 said:
You can only unlock the bootloader on the new Honor at the Honor office. The workers there have such smartphones, I have a friend among such workers and he made a request for me in a friendly way. I think that you will not see such a photo anywhere else. Alas, as long as it's useless, I need a custom one Recovery, But I don't know where to get it.
Click to expand...
Click to collapse
Well that's... disappointing... can't believe we have to even consider that. In my case, we don't have those centers, so I'm definitely screwed... good job Honor...

Categories

Resources