Database Info

[Q] Soft Bricked - No storage - Wont flash stock recovery

I was texting on my phone when it crashed. I was running SlimKat official release with franco kernel 25 for two weeks. Phone had been running great! Now it bootloops on the google logo and doesn't recognize the 32gb of memory. Wont mount any of the partitions in recovery. When in recovery (TWRP) and I opt to reboot to bootloader or reboot is says NO OS. Now as well all I can do with fastboot is relock the phone. I wanted to reflash the recovery to stock as Google will exchange the phone. When I try and flash the stock recovery in the terminal command window everything looks like its flashing good however when I boot into recovery it still boots TWRP.
Help please. :crying:

what do you mean all you can do is relock the phone in fastboot? that doesnt make sense.
what commands are you trying to do when you flash the stock recovery?

Flash the entire factory image. If you get errors your eMMC is probably toast and you should warranty it.
Sent from my Nexus 5

did you use toolkit for rooting?

Simonna said:
did you use toolkit for rooting?
Click to expand...
Click to collapse
You ask because of his troubleshooting expertise or because you think that toolkits and CF.. are killing emmc?
I have seen this problem from people using the manual method and the toolkits as well.
I strongly think that the question to ask is whether they have a 16GB or 32GB phone.

GUGUITOMTG4 said:
You ask because of his troubleshooting expertise or because you think that toolkits and CF.. are killing emmc?
I have seen this problem from people using the manual method and the toolkits as well.
I strongly think that the question to ask is whether they have a 16GB or 32GB phone.
Click to expand...
Click to collapse
I think that toolkits are killing emmc because I saw more users who used toolkits for rooting, and then their phones just dead.But maybe it's just a coincidence..

Toolkits does not kill emmc. This is just coincidence.
emmc died on the phone
Tapatalk-kal küldve az én Nexus 5-el

Simonna said:
I think that toolkits are killing emmc because I saw more users who used toolkits for rooting, and then their phones just dead.But maybe it's just a coincidence..
Click to expand...
Click to collapse
I don't think it's tool kits either. Keep in mind that more people use tool kits than don't. So even though you see more of what appears to be emmc failure with tool kit users there are more of them. I've seen it with people who have not used tool kits a well as those that have.
Sent from my Nexus 5

jd1639 said:
I don't think it's tool kits either. Keep in mind that more people use tool kits than don't. So even though you see more of what appears to be emmc failure with tool kit users there are more of them. I've seen it with people who have not used tool kits a well as those that have.
Sent from my Nexus 5
Click to expand...
Click to collapse
It's not toolkits. It's the luck of the draw. How many N5's sold compared to how many that have had fried nand is what needs to be looked at. That figure is going to be very hard to come by. It could be a normal percentage of failure or it could be high or low. Did Google cheap out on the memory to make the phone more affordable? Or did they put quality memory in and cut some other corners as well as cut their profit margin? All questions that none of us on XDA will, most likely, ever know. The one thing you can be certain of though, toolkits aren't the cause of these failures.

I also had this problem, I couldn't do anyting. I left it sitting there for the night.
The next morning, it booted up like nothing happened

El Daddy said:
Flash the entire factory image. If you get errors your eMMC is probably toast and you should warranty it.
Sent from my Nexus 5
Click to expand...
Click to collapse
Google says they will warranty it however the bootloader wont stay locked and fastboot says it successfully flashes the stock recovery.
But when I reboot the phone into bootloader it says unlocked again and the recovery stays TWRP no matter what I flash. Im lost. It doesn't make any sense....
Looks like I may have to send it in as is however I'm concerned they wont warranty it when they get it back unlocked with TWRP.

{
"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"
}
rooteddesire said:
google says they will warranty it however the bootloader wont stay locked and fastboot says it successfully flashes the stock recovery.
But when i reboot the phone into bootloader it says unlocked again and the recovery stays twrp no matter what i flash. Im lost. It doesn't make any sense....
Looks like i may have to send it in as is however i'm concerned they wont warranty it when they get it back unlocked with twrp.
Click to expand...
Click to collapse

Zepius said:
what do you mean all you can do is relock the phone in fastboot? that doesnt make sense.
what commands are you trying to do when you flash the stock recovery?
Click to expand...
Click to collapse
fastboot flash recovery recovery.img
fastboot oem lock
and so on....
it says its successful, however its obviously not.

RootedDesire said:
fastboot flash recovery recovery.img
fastboot oem lock
and so on....
it says its successful, however its obviously not.
Click to expand...
Click to collapse
Then I reboot and get this
its definitely the stock recovery i extracted and placed in my fastboot folder

RootedDesire said:
Google says they will warranty it however the bootloader wont stay locked and fastboot says it successfully flashes the stock recovery.
But when I reboot the phone into bootloader it says unlocked again and the recovery stays TWRP no matter what I flash. Im lost. It doesn't make any sense....
Looks like I may have to send it in as is however I'm concerned they wont warranty it when they get it back unlocked with TWRP.
Click to expand...
Click to collapse
That's because your eMMC is dead. It can't be written to.
Sent from my Nexus 5

yet another brick in the wall
Just got the same issue. TWRP show internal storage size 0. Can't flash anything. Can't lock.
Is somebody researching this problem? I have several JetFlash USB drives. Sometimes they becomes read-only. But with their software I can "unbrick" these drives. Maybe, we can find a solution for our Nexus 5. I can participate in testing.

XeeV said:
Just got the same issue. TWRP show internal storage size 0. Can't flash anything. Can't lock.
Does somebody researching this problem? I have several JetFlash USB drives. Sometimes they becomes read-only. But with their software I can "unbrick" these drives. Maybe, we can find a solution for our Nexus 5. I can participate in testing.
Click to expand...
Click to collapse
Highly unlikely. AFAIK when your eMMC is dead, it's dead forever.

exb0 said:
Highly unlikely. AFAIK when your eMMC is dead, it's dead forever.
Click to expand...
Click to collapse
But it's not dead. It is readable. I can't write. But, maybe there is a workaround like with JetFlash USB drives. I have 2 JetFlash sticks. They became read-only: I could read, but could't write, even with dd or fdisk (they works OK, but after reinserting everything is as it was before). But there is a software: it erases JetFlash drives and I can write again.

XeeV said:
Just got the same issue. TWRP show internal storage size 0. Can't flash anything. Can't lock.
Is somebody researching this problem? I have several JetFlash USB drives. Sometimes they becomes read-only. But with their software I can "unbrick" these drives. Maybe, we can find a solution for our Nexus 5. I can participate in testing.
Click to expand...
Click to collapse
I had the same issue yesterday, I reflashed stock via fastboot and it fixed the issue, I couldnt flash/wipe/connect to adb or anything, when I tried to mount it showed internal storage size 0, so I went back to the bootloader and flashed all the stock stuff via fastboot and it did the trick for me.

Pawelss said:
I had the same issue yesterday, I reflashed stock via fastboot and it fixed the issue, I couldnt flash/wipe/connect to adb or anything, when I tried to mount it showed internal storage size 0, so I went back to the bootloader and flashed all the stock stuff via fastboot and it did the trick for me.
Click to expand...
Click to collapse
I can reflash a stock, but it writes nothing. It only shows, that it's writing. I can flash CWM instead TWRP. But after a reboot there will be my old TWRP. I can do "fastboot oem lock" and it show "locked", but after reboot it show "unlocked". All is read-only but no errors when writing.
---------- Post added at 09:17 PM ---------- Previous post was at 09:00 PM ----------
Nexus 5 has Sandisk SDIN8DE4. In datasheet there is "Enhanced Write Protection":
----------------------------------------------------------------------------------------------------------------------------------------
To allow the host to protect data against erase or write, the iNAND supports two levels of write
protect command 10 :
• The entire iNAND (including the Boot Area Partitions, General Purpose Area Partition, and
User/Enhanced User Data Area Partition) may be write-protected by setting the permanent
or temporary write protect bits in the CSD.
• Specific segments of the iNAND may be permanently, power-on or temporarily write
protected. Segment size can be programmed via the EXT_CSD register.
For additional information please refer JESD84-A441 standard.
----------------------------------------------------------------------------------------------------------------------------------------
and "H/W Reset":
----------------------------------------------------------------------------------------------------------------------------------------
Hardware reset may be used by host to reset the device, moving the card to a Pre-idle state and
disabling the power-on period write protect on blocks that was set as power-on write protect before
the reset was asserted. For more information, refer to JESD84-A441 standard.
----------------------------------------------------------------------------------------------------------------------------------------
Maybe, there is a way to turn off write protection of just do a hardware reset (but no to loose bootloader)?
Is anybody here familiar with eMMC, chips and JESD84-A441 standard?

[Q] my atrix 2 does not turn on !!

I rooted my atrix 2, i installed BBM and reboot my mobile and install mokee 4.4.2
after that my atrix 2 is not booting allthough it show Motorola "M" sign and than blank screen .i m not able to recover my mobile using BBM
.i m able to go into android recovery but not know what to do

Good thing I keep this in case I forgot:
If you don't have the original FW for your Atrix 2 anymore, you should download the PROPER ROM for your Atrix 2.
Download the AT&T version here:
http://sbf.droid-developers.org/phone.php?device=17
Doesn't matter if GB or ICS. First time you did it is via ICS though. Just make sure it is an AT&T FXZ file, not Retail Asia, Chinese or Indian. AT&T *AT&T*!!!!
Download proper drivers for your phone
Download RSDLite
Follow this guide
http://forum.xda-developers.com/showthread.php?t=1396650
--or--
Turn off
Remove battery
Make sure you uncompressed the FXZ
Attach battery
Press Vol UP, DOWN and POWER simultaneously
Select AP Fastboot
On RSD Lite:
Select the FXZ file
Connect USB
Start FLASHING!
AND WAIT!
Wait until the "Please power up manually the phone" shows up in RSDLite
Power the phone up
Do not close the RSDLite yet, wait 'til it says FINISHED
Okay?
Click to expand...
Click to collapse
Well, I have the AT&T version of the Atrix 2 so I should download *ONLY* AT&T ROM.
In your case, it does matter if your phone is AT&T or Asian models. Please download the correct FXZ for your phone.
Good luck! :good:
Cheers,
Rae

Raeshabu said:
Good thing I keep this in case I forgot:
Well, I have the AT&T version of the Atrix 2 so I should download *ONLY* AT&T ROM.
In your case, it does matter if your phone is AT&T or Asian models. Please download the correct FXZ for your phone.
Good luck! :good:
Cheers,
Rae
Click to expand...
Click to collapse
it give me this result * failed flashing process 7/21 flash ''cdt.bin'' *

mohaegy said:
it give me this result * failed flashing process 7/21 flash ''cdt.bin'' *
Click to expand...
Click to collapse
I really didn't have this kind of error when I was flashing my A2.
Maybe you could try it in a different PC.
I should ask, what ROM version did you download (ICS or GB)? And what model is your phone, AT&T (MB865) or Asian models (ME865)?
- Rae

Raeshabu said:
I really didn't have this kind of error when I was flashing my A2.
Maybe you could try it in a different PC.
I should ask, what ROM version did you download (ICS or GB)? And what model is your phone, AT&T (MB865) or Asian models (ME865)?
- Rae
Click to expand...
Click to collapse
i tried ICS and GB
my model AT&T mb865
(

mohaegy said:
i tried ICS and GB
my model AT&T mb865
(
Click to expand...
Click to collapse
If you've already attempted flashing ICS on your AT&T Atrix 2 then DO NOT try to flash GB. It WILL brick your phone, that is, if it hasn't already. There is only one FXZ that you can flash on that phone and that is the AT&T ICS FXZ. Find and download that before trying anything else.
( @Raeshabu already gave you all the info and links that you need. )

1BadWolf said:
If you've already attempted flashing ICS on your AT&T Atrix 2 then DO NOT try to flash GB. It WILL brick your phone, that is, if it hasn't already. There is only one FXZ that you can flash on that phone and that is the AT&T ICS FXZ. Find and download that before trying anything else.
( @Raeshabu already gave you all the info and links that you need. )
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"
}
help plz i can't doing anything after that !

1BadWolf said:
If you've already attempted flashing ICS on your AT&T Atrix 2 then DO NOT try to flash GB. It WILL brick your phone, that is, if it hasn't already. There is only one FXZ that you can flash on that phone and that is the AT&T ICS FXZ. Find and download that before trying anything else.
( @Raeshabu already gave you all the info and links that you need. )
Click to expand...
Click to collapse
Thanks for clarifying that, I didn't know that until now. Thanks!
mohaegy said:
View attachment 2792371
help plz i can't doing anything after that !
Click to expand...
Click to collapse
Oh no!
You have flashed Retail Asia (MEARET) version of the FXZ. I really don't know if you will be able to flash anything again after that.
Could you tell if your A2 has AT&T logo below the home keys? If yes, then you SHOULD download and flash ONLY AT&T FXZ.
I suggest flashing the ICS ROM as that is the one that worked for me.
And also, if you're using a PC please use the USB ports in the back panel as much as possible. And keep your battery charged! :good:
Good luck!
- Rae

Raeshabu said:
Thanks for clarifying that, I didn't know that until now. Thanks!
Oh no!
You have flashed Retail Asia (MEARET) version of the FXZ. I really don't know if you will be able to flash anything again after that.
Could you tell if your A2 has AT&T logo below the home keys? If yes, then you SHOULD download and flash ONLY AT&T FXZ.
I suggest flashing the ICS ROM as that is the one that worked for me.
And also, if you're using a PC please use the USB ports in the back panel as much as possible. And keep your battery charged! :good:
Good luck!
- Rae
Click to expand...
Click to collapse
i will try this solution . thank you
can i root my phone with this situation

Raeshabu said:
Thanks for clarifying that, I didn't know that until now. Thanks!
Click to expand...
Click to collapse
Sure thing! I found out the hard way that's why I recommend everybody do as much reading as possible when dealing with this device especially.
mohaegy said:
i will try this solution . thank you
can i root my phone with this situation
Click to expand...
Click to collapse
Yes, after you get the proper FXZ flashed rooting is pretty simple.

1BadWolf said:
Sure thing! I found out the hard way that's why I recommend everybody do as much reading as possible when dealing with this device especially.
Yes, after you get the proper FXZ flashed rooting is pretty simple.
Click to expand...
Click to collapse
same problem

mohaegy said:
View attachment 2793974
same problem
Click to expand...
Click to collapse
Hey, I Googled your problem and it seems that it might be because:
1. RSD Lite does not recognize your phone
2. You don't have the correct drivers for your device.
2. Your USB cable might be faulty
Although, I am not 100% sure if these were the cause of your problems, but it might be...
Edit:
I have experienced your situation just moments ago. My A2 won't get past the mbm flashing.
I think your battery's power is too low for it to accept any flashing. I charged my phone up until 30% and tried flashing again, and voila it got through all of it.
I suggest you charge your phone again with a wall charger (to a wall socket), not on your PC. If it got through the charging screen, you're one lucky guy like me.
***
So, let's narrow up your problem..
1. Have you tried using a different USB cable?
2. Or on a different USB port?
3. Have you installed proper Motorola Drivers?
4. Have you got any message from Fastboot that your "Battery is too low"
I recommend downloading this file: http://www.mediafire.com/download/51gmzrtjx4vrmed/Tools.rar
The zip file have the Motorola drivers, RSD Lite, ICS Root and Boot Menu Manager.
Credits to arnab.
***
Install first the Motorola drivers before you flash again.
Good luck!
- Rae

Sony Xperia Z3 Ask Away- help thread.

[SIZE=+2][SIZE=+2][SIZE=+2]Thread created by TonyStark:
(To honor our departed colleague TonyStark, please continue to use this thread, MikeChannon Forum Admin)
[/SIZE][/SIZE][/SIZE][SIZE=+2] [SIZE=+2]
Welcome to[/SIZE][/SIZE]
[SIZE=+2][SIZE=+2] Questions Answers & Troubleshooting [/SIZE][/SIZE]
[SIZE=+2][SIZE=+2]
{
"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"
}
[/SIZE] [/SIZE]​[SIZE=+2] This P2P thread has been created to assist owners of:[/SIZE]
[SIZE=+2]The SONY Xperia Z3[/SIZE]
There are no questions that are deemed insignificant
Helpful information for your device:
Full device specifications
USB Drivers (scroll to your device and download)
Sony PC Companion (Download)
Bridge for Mac (Download)
ᴥAsk Awayᴥ
Please feel free to ask anything related to your device.​

Hi! I unlocked my Z3 without backupping, so I lost the drm keys. I know there is a way to fix it on the part of camera, sound, etc. But will the Sony upgrades come as normal?
Sent from my D6603 using XDA Free mobile app

juustonen said:
Hi! I unlocked my Z3 without backupping, so I lost the drm keys. I know there is a way to fix it on the part of camera, sound, etc. But will the Sony upgrades come as normal?
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
Hi,
Pardon me for saying this, but it's never a good idea to unlock your phone without making a backup beforehand. AFAIK, Sony upgrades will not come to unlocked phones as normal, so I would advice you to make a backup now and reset the device to the factory settings. I know that's a pain in the ass and a hell of a job, but IMO this is the only way to "repair" your device. If this does not work for you, alas you have to reset your device entirely.
kindest regards. kuzibri

Will the drm keys come back that way?
Sent from my D6603 using XDA Free mobile app

juustonen said:
Will the drm keys come back that way?
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
Do not know for sure, but I know that resetting your device to factory settings, gives you back your original Z3, so probably also your drmkeys and your factory warranty, cause when you unllock your device, you loose the warranty anyway.
kindest regards, kuzibri

juustonen said:
Will the drm keys come back that way?
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
I thought if you re-locked the bootloader you can use PC Companion or Sony Update Service to repair to stock. Not sure if it restores drm or camera stuff.

I'll be getting the Z3 in a couple of days. Some things I want to check because I've been away from Sony phones for a while(last one I had was an Xperia S).
So to root it is still recommended to downgrade to Kitkat and root using this method, as well as recovery? That procedure will not break my DRM keys(I remember unlocking bootloader caused that on my Xperia S). Afterwards I can just flash a .zip file and update to the latest 5.1 ROM?
One other thing; before I start tempering with my phone in any way, is it possible to back up DRM keys/EFS partition or whatever without root? Someone please link me some guide which will get me completely backed up. I know my DRM keys are safe until I unlock my bootloader(which I won't do) but I'd still like to back up while everything is stock, you never know.

revan17 said:
I'll be getting the Z3 in a couple of days. Some things I want to check because I've been away from Sony phones for a while(last one I had was an Xperia S).
So to root it is still recommended to downgrade to Kitkat and root using this method, as well as recovery? That procedure will not break my DRM keys(I remember unlocking bootloader caused that on my Xperia S). Afterwards I can just flash a .zip file and update to the latest 5.1 ROM?
One other thing; before I start tempering with my phone in any way, is it possible to back up DRM keys/EFS partition or whatever without root? Someone please link me some guide which will get me completely backed up. I know my DRM keys are safe until I unlock my bootloader(which I won't do) but I'd still like to back up while everything is stock, you never know.
Click to expand...
Click to collapse
Yes, that method will work.
As soon as you have root and a custom recovery, you can back up everything. With Backup TA, it's possible to back up and restore the DRM partition.
---------- Post added at 08:41 PM ---------- Previous post was at 08:35 PM ----------
And now for my own question.
What's the deal with the Z3's kernel and recoveries? I'm on a rooted 5.1.1 without an unlocked bootloader, but with TWRP and CWM from XZDualRecovery.
Why do you need to unlock the device to flash a kernel? How is the kernel attached to the bootloader and why does XZDR work, even providing two recoveries? Is the main ROM image just modified so it will can load the recovery before Android itself and the recovery partition is intact? How are kernels and recoveries connected? I see all kernel threads mentioning included recoveries.
This is really weird, but I came from a Galaxy Nexus where the recovery partition was separate from the system partition and where flashing kernels was a normal thing. Kernels and recovery had absolutely nothing to do with each other.

Toledo_JAB said:
I thought if you re-locked the bootloader you can use PC Companion or Sony Update Service to repair to stock. Not sure if it restores drm or camera stuff.
Click to expand...
Click to collapse
Hi,
In principle, you're right, but I also do not know for sure if everything will be working as it should before, especially the drm and/or camera.
kindest regards, kuzibri
---------- Post added at 22:03 ---------- Previous post was at 21:45 ----------
revan17 said:
I'll be getting the Z3 in a couple of days. Some things I want to check because I've been away from Sony phones for a while(last one I had was an Xperia S).
So to root it is still recommended to downgrade to Kitkat and root using this method, as well as recovery? That procedure will not break my DRM keys(I remember unlocking bootloader caused that on my Xperia S). Afterwards I can just flash a .zip file and update to the latest 5.1 ROM?
One other thing; before I start tempering with my phone in any way, is it possible to back up DRM keys/EFS partition or whatever without root? Someone please link me some guide which will get me completely backed up. I know my DRM keys are safe until I unlock my bootloader(which I won't do) but I'd still like to back up while everything is stock, you never know.
Click to expand...
Click to collapse
Hi,
why do you want to unlock your new Z3, thereby loosing your warranty, to downgrade to Kitkat? I just would suggest to use Lolllipop for a while on your new Z3 before making that decision. I have Lollipop also, and although I had to get used to it, it's way far better that Kitkat. Just my 2 cents.
kindest regards, kuzibri

kuzibri said:
Hi,
In principle, you're right, but I also do not know for sure if everything will be working as it should before, especially the drm and/or camera.
kindest regards, kuzibri
---------- Post added at 22:03 ---------- Previous post was at 21:45 ----------
Hi,
why do you want to unlock your new Z3, thereby loosing your warranty, to downgrade to Kitkat? I just would suggest to use Lolllipop for a while on your new Z3 before making that decision. I have Lollipop also, and although I had to get used to it, it's way far better that Kitkat. Just my 2 cents.
kindest regards, kuzibri
Click to expand...
Click to collapse
I am not going to unlock my bootloader at all. I'll only downgrade to kitkat so I can root the phone and install custom recovery, afterwards I'll flash stock LP. I don't think you can root LP without using Kingroot, which sends some info to chinese server which I do not want.

revan17 said:
I am not going to unlock my bootloader at all. I'll only downgrade to kitkat so I can root the phone and install custom recovery, afterwards I'll flash stock LP. I don't think you can root LP without using Kingroot, which sends some info to chinese server which I do not want.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3108230
[ROOT] [XPERIA Z2/Z3] [ANDROID 5 LOLLIPOP EASY ROOT] [new] [V2]
You can use kingroot safely.Many of us have used it and there is no longer an issue of malware or ads.
Sent from my D6503 using Tapatalk

revan17 said:
I am not going to unlock my bootloader at all. I'll only downgrade to kitkat so I can root the phone and install custom recovery, afterwards I'll flash stock LP. I don't think you can root LP without using Kingroot, which sends some info to chinese server which I do not want.
Click to expand...
Click to collapse
yep, do it like that.. downgrade-root-backup TA-flash L
I too wouldn't recommend using kingroot.

schetz said:
yep, do it like that.. downgrade-root-backup TA-flash L
I too wouldn't recommend using kingroot.
Click to expand...
Click to collapse
No need to back up TA if you are not unlocking the boot loader

gregbradley said:
No need to back up TA if you are not unlocking the boot loader
Click to expand...
Click to collapse
Yep, I know. But one day he might do that, and while he's at rooting, extra 2 minutes won't hurt. But you are right in a way I should have mentioned that

Big help required please
Mine wont charge beyond 1%.
I plug in the charger with phone off and the red notification light comes on followed by the Sony Xperia startup screen, after about 4 seconds the red light goes off and does not come on again. The screen then changes to an image of a large battery displaying 1%. When I press and hold the power button the device turns on as normal but given that the battery is only 1% it doesnt even last a minute. I have had it upto 12% at one point (not sure how as I didnt do anything differently) and the power drained that quickly when turned on it went down 1% about every 10 seconds.
Im on T-Mobile using a D6603 stock unmodified in any way. I have tried hold vol up and power button, hold vol down and also I have pressed the yellow button beside the sim card. I have had it on charge nearly 2 full days and Im now at breaking point. I appreciate I may be due an update but as you can see my phone says different. Pictures included
(This post is in another thread but wasnt getting much help, so reposted here)

homer4president said:
Big help required please
Mine wont charge beyond 1%.
I plug in the charger with phone off and the red notification light comes on followed by the Sony Xperia startup screen, after about 4 seconds the red light goes off and does not come on again. The screen then changes to an image of a large battery displaying 1%. When I press and hold the power button the device turns on as normal but given that the battery is only 1% it doesnt even last a minute. I have had it upto 12% at one point (not sure how as I didnt do anything differently) and the power drained that quickly when turned on it went down 1% about every 10 seconds.
Im on T-Mobile using a D6603 stock unmodified in any way. I have tried hold vol up and power button, hold vol down and also I have pressed the yellow button beside the sim card. I have had it on charge nearly 2 full days and Im now at breaking point. I appreciate I may be due an update but as you can see my phone says different. Pictures included
(This post is in another thread but wasnt getting much help, so reposted here)
Click to expand...
Click to collapse
Hi,
nasty problem. Guessing the charger is connected to a wall outlet:
1. Did you already tried a different/new USB cable, if not, please do so and see if the problem is solved?
2. Did you already tried to charge with the phone on?
3. If these things do not work, you probably have a battery issue and have to send it in for a new one.
good luck and kindest regards, kuzibri

Thanks for your reply
Yes it has been plugged into the wall, laptop and car charger both turned on and off.
I have tried the supplied charger and a number of others. I thought it was gonna be a case of sending it away. Thats not good given that the phone isnt even 6 months old. do you suppose its the battery itself? If so surely i could replace it myself?

homer4president said:
Thanks for your reply
Yes it has been plugged into the wall, laptop and car charger both turned on and off.
I have tried the supplied charger and a number of others. I thought it was gonna be a case of sending it away. Thats not good given that the phone isnt even 6 months old. do you suppose its the battery itself? If so surely i could replace it myself?
Click to expand...
Click to collapse
Hi,
regarding this: "If so surely i could replace it myself", I strongly advice you NOT to do that cause you're voiding your warranty with opening up the device.Did you tried another USB Cable??
kindest regards, kuzibri

Fair point. Yes tried a number of different cables and chargers
Sent from my C2105 using XDA Free mobile app

homer4president said:
Fair point. Yes tried a number of different cables and chargers
Sent from my C2105 using XDA Free mobile app
Click to expand...
Click to collapse
Ok my friend, so it's a case of sending it for repair I'm afraid
kindest regards, kuzibri

[Rom] Bootloader Recover Huawei Watch 2 BT LEO-B09/LEO-BX9

Hi Everyone,
As some of you have tested the first firmware (4G) available in the Bluetooth version, our friend @mcdull and @sorayahya have fixed a broken Watch using below firmware.
Sorayahya will post the manual in this same thread so all of you can make your watches functional again.
Link: https://mega.nz/#!gqQATbga
Decryption key: !mD2smD4jEq_FOkhE1uy0PQ5uf6XYpxR0wxxkM6msPiE
Special thanks to @mcdull for preparing this file to all of us.

So after downloading the above files from dr_chch's post extract the files. After that we will need to get QPST which has the program called QFIL which we will be using to unbrick the watch.
Download “QPST 2.7 (QFIL)” from HERE and extract it to an empty folder. Install QPST by double clicking setup.exe.
Now you want to plug in your Huawei Watch 2 to the PC using the charging cable that came with the watch.
At first you might get a notification from the PC that the usb device is unknown, if that happens you will need to hold down on your watch's right top button for around 30 seconds. After that you should get a notification from your PC that a new device was plugged in and it will start to install a new driver. Once that's done you should have a "Qualcomm HS-USB QDLoader 9008" device show up in your device manager.
{
"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"
}
We won't be needing the storage device to show up so if it doesn't for you that's alright.
Next we will open QFIL from start menu, if it's not in the start menu you can locate it by going to Program Files\Qualcomm\bin\. You should see "Qualcomm HS-USB QDLoader 9008" written on the top, if it's not then click on the "SelectPort" button and then select "Qualcomm HS-USB QDLoader 9008". After that Insert all the necessary file needed by QFIL:
(1)The programmer will be prog_emmc_firehose.mbn;
(2)Use the rawprogram0.xml;
(3)Use the patch0.xml;
(4)Hit “Download” button.
If the process you did with QFIL finished successfully, the watch will boot again. If not then try to restart the program and repeat the same process again until you succeed.
At this point your watch is alive again but without a firmware so you will need to flash the correct ROM through fastboot.
For that you can check out the guide dr_chch made here:
https://forum.xda-developers.com/watch-2/development/rom-huawei-watch-2-bt-leo-b09-leo-bx9-t3616779

Thanks for the files and the recovery guide. Please make sure you understand the below before your recovery.
1. You will probably lost the original MAC Address of your WIFI and Bluetooth. But at least the device will work with both functions, it will assign another MAC Address for you.
2. The recovery file includes only the boot loader, you still need to boot into fastboot (holding the device power button until you feel it vibrate. Then quickly release and press the power buttons) to flash the latest ROM downloaded from here.

Mod Edit
what you can help?

dr_chch said:
Hi Everyone,
As some of you have tested the first firmware (4G) available in the Bluetooth version, our friend @mcdull and @sorayahya have fixed a broken Watch using below firmware.
Sorayahya will post the manual in this same thread so all of you can make your watches functional again.
Am getting an error accessing the mega link.
Click to expand...
Click to collapse

kenmlax said:
dr_chch said:
Hi Everyone,
As some of you have tested the first firmware (4G) available in the Bluetooth version, our friend @mcdull and @sorayahya have fixed a broken Watch using below firmware.
Sorayahya will post the manual in this same thread so all of you can make your watches functional again.
Am getting an error accessing the mega link.
Click to expand...
Click to collapse
kenmlax said:
Was this solution ever shared cause ive been waiting for it for quite some time now... my huwei watch model is LEO-DLXX
Click to expand...
Click to collapse
You wont need this file as this is for de-bricking the BT version only.
And the mega link works just fine.
Click to expand...
Click to collapse

mcdull said:
kenmlax said:
You wont need this file as this is for de-bricking the BT version only.
And the mega link works just fine.
Click to expand...
Click to collapse
Is there a way to unbrick the 4g version of this watch. specifically the LEO-DLXX
Click to expand...
Click to collapse

kenmlax said:
mcdull said:
Is there a way to unbrick the 4g version of this watch. specifically the LEO-DLXX
Click to expand...
Click to collapse
If you noticed all the quote, reply, pm name... I have answered you MANY times.
Click to expand...
Click to collapse

Code:
Start Download
Program Path:C:\Leo\prog_emmc_firehose.mbn
COM Port number:7
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
I'm getting this error. I tried multiple Desktop's and win7/10

Just learned of this thread......
I am wondering if anyone got the LEO-DLXX Watch 2 4G working again? Mine is recognized in QFIL as a qualcomm 9008, but that is as far as I can get. Has anyone been able to get the bootloader working with the files in this thread? I'm not sure what happened to mine, but it got bricked while installing the global ROM Huawei2_NXG46W_Global_4G. It is strange how it worked for so many people, but not mine. Any help or guidance is appreciated.

stephen1981 said:
I am wondering if anyone got the LEO-DLXX Watch 2 4G working again? Mine is recognized in QFIL as a qualcomm 9008, but that is as far as I can get. Has anyone been able to get the bootloader working with the files in this thread? I'm not sure what happened to mine, but it got bricked while installing the global ROM Huawei2_NXG46W_Global_4G. It is strange how it worked for so many people, but not mine. Any help or guidance is appreciated.
Click to expand...
Click to collapse
it worked for me

I tried many times now and still get the error message.
Also i've used all of the program build's
Is there anyone who can assist me in this process?

luciano1961 said:
it worked for me
Click to expand...
Click to collapse
The ROM worked for you or were you able to recover the boot loader? Has the LEO-L09S recovery found here: https://forum.xda-developers.com/watch-2/help/flashed-huawei-watch2-power-t3632341 worked for anyone?
basziee said:
I tried many times now and still get the error message.
Also i've used all of the program build's
Is there anyone who can assist me in this process?
Click to expand...
Click to collapse
Are you getting the sahara protocol error message as well? Are you trying to use QFIL to restore the bootloader on the LEO-DLXX watch?
Two strange things happened when flashing the ROM from this thread: https://forum.xda-developers.com/watch-2/development/rom-huawei-watch-2-4g-l-09s-global-t3602205
First, it took a very long time for the device to show up with adb devices. There was a device there, but it wasn't listing every time I connected. As soon as I did, I went ahead but probably shouldn't have. Second, the fast boot process seemed to go along as normal (I have flashed a few ROMS, but never on a watch) until it came to the system. The system fast boot process took seconds....not longer than bootloader, boot, etc.... That is something I have not experienced before and thought it may have to do with a smaller system for android wear, but in fact it is not that small. After that, well it is bricked, but at least showing as a qualcomm disk.
I guess I have to wait until the recovery bootloader (firehose, rawprogram etc..) is leaked for the LEO-DLXX device. There is no possibility of returning the device or paying for service since it was bought in China and brought to Canada where it hasn't even been released yet.

stephen1981 said:
Are you getting the sahara protocol error message as well? Are you trying to use QFIL to restore the bootloader on the LEO-DLXX watch?
Click to expand...
Click to collapse
Yes everytime I tried to flash the .mbm file I get the sahara protocol error saying it is 0 bytes.
I also tried draining the battery fully and I switched between many desktop's
And still no luck
And quick question: my friend has the same watch. Can i do something with that to fix my own?

Has anyone successfully flashed the Huawei Watch 2 Pro (LEO-DLXXU)?
I'm keen to get my watch compatible with Play store apps rather than Huawei App Store, but I'd be keen to hear from someone who has been successful.

Hi @dr_chch, do you have the files for DLXX ? I tried to flash the Google P preview forgeting that I have a 4G and not BT model and It totally bricked my watch...

Supercairos said:
Hi @dr_chch, do you have the files for DLXX ? I tried to flash the Google P preview forgeting that I have a 4G and not BT model and It totally bricked my watch...
Click to expand...
Click to collapse
same here, i just wish someone would help us find the right files for the 4G version.

Same problem with my LEO-DLXX. I noticed that 1 of 3 files needed to flash has wrong name
rawprogram_unsparse.xml , nor rawprogram0.xml
Is there a problem with this?

Supercairos said:
Hi @dr_chch, do you have the files for DLXX ? I tried to flash the Google P preview forgeting that I have a 4G and not BT model and It totally bricked my watch...
Click to expand...
Click to collapse
You mean Oreo?

hackintosh5 said:
You mean Oreo?
Click to expand...
Click to collapse
Nope he means P as in this

How To Guide [CLOSED] Bypass the region check in Lenovo p12 pro 12.6(CN version)

Having had a long research after I bricked my lenovo p12 pro 12.6(the CN version) ,I thought I finally figured out what is happening when boot ROW firmware on my tablet and a method to bypass such region check. Here is detail procedure:
First of all ,you DO NOT need to return your bricked tablet back to the seller or manufactures, any of which costs time and patience.
1、Download the super partition image file Mod edit: Links removed ,and extract super.img from it using 7z x ... command.
2、You can choose to use my bash shell script (flash_stock_firmware.sh)or your manual instructions: to flash the stock firmware
Bash:
bash 'flash_stock_firmware.sh' 'PATH/TO/THE/STOCK/FIRMWARE/FOLDER'
,it takes about 5 minutes to end.
{
"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"
}
After it booted to framework ,the init process will play a bootanimation ,in my case it shows :
This is exactly what we should to remove.And now you could reboot the tablet into fastboot mode
Code:
fastboot flash super PATH/TO/EXTRACTED/SUPER/IMAGE
fastboot erase userdata
fastboot erase metadata
fastboot reboot
In my case ,my tablet successfully launches the SetupWizard for registering device to google:

Wow fantastic work? Any chance you can elaborate anymore in your instructions for the more novice users? I've not used ADB before. When I tried and the tablet was broke ADB couldn't see the tablet where as QFIL could.
Does the boot loader have to be unlocked?
I'm still waiting for mine back from china but depending on the stability of the Global ROM I may move across.
Is the above doable only with ADB or can it also be done in QFIL?
Does the Global ROM successfully OTA for you or does it fail after download? Can you search from the settings menu?
Going forward are you able to use the Lenovo Recovery Centre to flash updates Global ROM's without having to do the steps above again?

mardon85 said:
Wow fantastic work? Any chance you can elaborate anymore in your instructions for the more novice users? I've not used ADB before. When I tried and the tablet was broke ADB couldn't see the tablet where as QFIL could.
Does the boot loader have to be unlocked?
I'm still waiting for mine back from china but depending on the stability of the Global ROM I may move across.
Is the above doable only with ADB or can it also be done in QFIL?
Does the Global ROM successfully OTA for you or does it fail after download? Can you search from the settings menu?
Going forward are you able to use the Lenovo Recovery Centre to flash updates Global ROM's without having to do the steps above again?
Click to expand...
Click to collapse
Edited

ZTE AXON 7 said:
otloader
2、fastboot boot rec/recovery.img(Here you should wait for about thirty seconds before initialization completed)
3、adb push systemrw_1.32_flashable.zip /sdcard
4、Go to Install->/sdcard/ and choo
Click to expand...
Click to collapse
ZTE AXON 7 said:
Edited
Click to expand...
Click to collapse
Thanks for this. Its the info I think a lot of us have been waiting for.
Did you find the following issues with your global ROM the same as the video below @ 27:14

That is some really good news, great work!

Thanks for sharing your work. However, could you kindly make the link available without requesting permission asking to share our gmail address with you?

Thanks!

ZTE AXON 7 said:
h costs time and patience.
1、Download the super partition image file Mod edit: Link removed ,and extract super.img from it using 7z x ... command.
Click to expand...
Click to collapse
famaTV said:
Thanks for sharing your work. However, could you kindly make the link available without requesting permission asking to share our gmail address with you?
Click to expand...
Click to collapse
Download link was updated

Thanks for updating download links.
Once these changes have been updated can we simply download and flash newer ROW ROM's?
How is your device performing, any glitches?

ZTE AXON 7 said:
Download link was updated
Click to expand...
Click to collapse
Thanks … but even the other website requests mobile number or email address to download.
Too much work and privacy exposure to take. I would wait for someone else to re-upload the file to a more straight forward user friendly site.
Meanwhile, what have you changed to the super.img to make it bypass the region check? Do you have the CN full firmware file?
On the other hand, with your fix, will the tablet update firmware OTA without any issues?
Thanks again.

ZTE AXON 7 said:
EXTRAC
Click to expand...
Click to collapse
mardon85 said:
Thanks for updating download links.
Once these changes have been updated can we simply download and flash newer ROW ROM's?
How is your device performing, any glitches?
Click to expand...
Click to collapse
So far so good, all works fine ,120hz refresh rate,precision 3 pencil ,precisicion keyboard,fast charging,etc...

There is a brand new ROM out today. Are you able to flash that now? Have you tried changing the region code via a hex editor?
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com

famaTV said:
Thanks … but even the other website requests mobile number or email address to download.
Too much work and privacy exposure to take. I would wait for someone else to re-upload the file to a more straight forward user friendly site.
Meanwhile, what have you changed to the super.img to make it bypass the region check? Do you have the CN full firmware file?
On the other hand, with your fix, will the tablet update firmware OTA without any issues?
Thanks again.
Click to expand...
Click to collapse
I updated to S212017 with this super image ,no problem:

ZTE AXON 7 said:
I updated to S212017 with this super image ,no problem:
View attachment 5506983
Click to expand...
Click to collapse
Is that via QFIL or OTA and also can you check if the search box works within the settings menu.

mardon85 said:
Is that via QFIL or OTA and also can you check if the search box works within the settings menu.
Click to expand...
Click to collapse
OTA,I changed the original ota update logic from aosp.

ZTE AXON 7 said:
OTA,I changed the original ota update logic from aosp.
Click to expand...
Click to collapse
Wow it seems you've cracked it even better than the Ali Express sellers. Most of the reports are that it can't OTA and the issue with the Settings search bar.
If mine ever clears Chinese customs (been stick there for 12days now) I'll get mine back and be able to play.

Ok I'm looking at your instructions.
The flashing of the stock firmware is the easy bit.
Once you do that you get the not compatible message as per your original instructions.
At this point the tablet is stuck in a screen similar to below. It does not matter which option you chose the tablet will reset back to the same screen.
What exactly do you do from this point to flash these instructions and your Super Image.
fastboot flash super PATH/TO/EXTRACTED/SUPER/IMAGE
fastboot erase userdata
fastboot erase metadata
fastboot reboot
If I try and run abd I get the following:
Sorry these are probably a no brainer with your capabilities but this is all quite new to me.
Basically I can see the tablet when Android is up and running but not from fastboot mode?

mardon85 said:
Ok I'm looking at your instructions.
The flashing of the stock firmware is the easy bit.
Once you do that you get the not compatible message as per your original instructions.
At this point the tablet is stuck in a screen similar to below. It does not matter which option you chose the tablet will reset back to the same screen.
View attachment 5507019
What exactly do you do from this point to flash these instructions and your Super Image.
fastboot flash super PATH/TO/EXTRACTED/SUPER/IMAGE
fastboot erase userdata
fastboot erase metadata
fastboot reboot
If I try and run abd I get the following:
View attachment 5507027
Sorry these are probably a no brainer with your capabilities but this is all quite new to me.
Basically I can see the tablet when Android is up and running but not from fastboot mode?
Click to expand...
Click to collapse
UPDATE... Fast boot commands do actually work. Even though it wont list devices commands like reboot work fine.
Did you have to unlock your bootloader for this? Have you kept widevine L1?

@ZTE AXON 7 you seem to be using Linux like me, mostly. I've used QFIL to flash the ROW ROMs but never did it from Linux. Do you have instructions on how to do that?
Oh wait, I reread your post. That script is for flashing the stock ROM, just like you said. Sorry about that.

Thank you for your work
I don't understand this very well. Do you have detailed operation steps?