Database Develop

Phone Bricked after JB update

Hi, i installed the last JB OTA update yesterday, and it worked great, but then i would install lum's roms, and i did it wrong. Since i can't boot, it shows the Motorola logo for about 30 sec, then i got blackscreen. All i can do is boot in motorola's recovery (not safestrap), or AP Flashboot.
Is there a way to restore my phone ?
Sorry for my poor english and thanks for your help.

Lightofdark said:
Hi, i installed the last JB OTA update yesterday, and it worked great, but then i would install lum's roms, and i did it wrong. Since i can't boot, it shows the Motorola logo for about 30 sec, then i got blackscreen. All i can do is boot in motorola's recovery (not safestrap), or AP Flashboot.
Is there a way to restore my phone ?
Sorry for my poor english and thanks for your help.
Click to expand...
Click to collapse
What exactly did you do? Did you flash Lum_UK's ROM over top of your stock ROM? And you can't you still get in to safestrap recovery? If that's the case you may be hosed until JB fastboot files come out. You could try to reflash the JB OTA in stock recovery. I have a feeling it will fail since your stock system has been modified but worth a shot.

kwyrt said:
What exactly did you do? Did you flash Lum_UK's ROM over top of your stock ROM? And you can't you still get in to safestrap recovery? If that's the case you may be hosed until JB fastboot files come out. You could try to reflash the JB OTA in stock recovery. I have a feeling it will fail since your stock system has been modified but worth a shot.
Click to expand...
Click to collapse
I replaced the system folder on my phone by the one of lum's rom with file manager into safestrap recovery (not smart i know). And I already try to reflash the update in the recovery but it didn't work. I'll have to wait untile JB fastboot files comes out and use my old Xperia mini pro
EDIT : Ok, i can update my phone to JB with recovery, but then the phone boots on AP flashboot automaticaly and says "flash failure"

You deleted the stock ROM and copied over the files from my ROM by hand?
That's not going to work as it will also delete safestrap recovery as you have found out.
The JB OTA update won't install as it is a patch that only applies to the stock ICS ROM.
Attempting to downgrade to the ICS fastboot files will perma-brick your phone. Some partitions are safe to flash, some can only be upgraded. Fortunately the system partition is flashable without that nasty issue!
However I've had a look at how Droid4utility actually flashes them and it seems it is possible to flash just the system partition in fastboot using:
moto-fastboot flash system.img
I have dumped the system partition from my phone and am currently uploading it. It will take an hour to upload and I'm out for the afternoon. Edit: It's here: http://d-h.st/oXt
You'll need Fastboot and the Motorola USB drivers
Install the USB drivers.
Decompress the system.img file you downloaded. Put it in the same directory as moto-fastboot.exe.
Ensure the battery in your phone has lots of charge.
Boot the phone into fastboot by holding down both volume buttons and pressing the power button.
Choose fastboot by pressing the vol down button until fastboot is highlighted, then press vol up.
Connect your USB cable.
Run moto-fastboot flash system.img
Run moto-fastboot reboot
Note: I have not tried this on my own phone, and I hope I never have to. It should work in theory.

when ever i have used moto-fastboot, i had to use 'moto-fastboot.exe' to get it to work
Sent from my Clear using xda premium
---------- Post added at 11:33 AM ---------- Previous post was at 10:38 AM ----------
not sure what exactly what you will need to flash for jellybean to unbrick
download
update.zip for your device and system version
moto-fastboot.exe mediafire
instructions
1. Enter android recovery and do a wipe data/factory and cache
2) Then reboot device to fastboot mode.(make sure to have all motorola drivers installed on your PC)
3) move the update Zip and the MOTO-FASTBOOT to a folder (ex. c:/Root)
4. unzip files
5) Open the CMD, and enter the these commands.
cd/
cd c:root
moto-fastboot.exe flash system system.img
moto-fastboot.exe reboot
also try renaming patch/boot.img.p to boot.img
moto-fastboot.exe boot boot.img
moto-fastboot.exe reboot
do not let battery die, phone requires software to charge battery,
if battery dies you will need a
TBH’s Motorola Programing Cable

The jellybean fast boot files are not available yet, but from the description of the fault it would seem that only the system partition is bricked.
Easiest way to tell is if the phone still charges. If it does then the boot.img is fine and you should leave it well alone. Just flash my system.img and you should be good to go.
If the phone doesn't charge then switch it off and wait for the jellybean fast boot to turn up, do not switch it on again until it does.
Please let us know how you got on.

Lum_UK said:
The jellybean fast boot files are not available yet, but from the description of the fault it would seem that only the system partition is bricked.
Easiest way to tell is if the phone still charges. If it does then the boot.img is fine and you should leave it well alone. Just flash my system.img and you should be good to go.
If the phone doesn't charge then switch it off and wait for the jellybean fast boot to turn up, do not switch it on again until it does.
Please let us know how you got on.
Click to expand...
Click to collapse
How can i know if the phone does charge or not ?

turn off phone connect to wall charger, if you get battery charging screen your good
if not it's not charging
if phone will not turn off, hold volume down and power for 15-20 secs

sd_shadow said:
turn off phone connect to wall charger, if you get battery charging screen your good
if not it's not charging
if phone will not turn off, hold volume down and power for 15-20 secs
Click to expand...
Click to collapse
when i plug the cable it automacialy boot in AP fastboot, it doesn't seems good

what does it say in ap fastboot.?
AP Fastboot Flaash Mode (S)
0A.74....

Well annoyingly, that file I was trying to upload for you... Windows 8 decided to go into sleep mode before it had finished uploading, starting again.
I'm also happy to try and dump any other partitions that may help, if someone can tell me how to do it.

sd_shadow said:
what does it say in ap fastboot.?
AP Fastboot Flaash Mode (S)
0A.74....
Click to expand...
Click to collapse
AP Fastboot Flash Mode (S) (Flash Failure)
0A.77

does android recovery have, this phone has been rooted code
qe 1/1
Click to expand...
Click to collapse
if not, you could try taking to verizon store, and tell them the new update bricked your phone
they will likely have to send it to get repaired, don't know if any verizon stores flash phones anymore
{
"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"
}

Well the system image is finally uploaded if you want to try it
http://d-h.st/oXt

sd_shadow said:
does android recovery have, this phone has been rooted code
if not, you could try taking to verizon store, and tell them the new update bricked your phone
they will likely have to send it to get repaired, don't know if any verizon stores flash phones anymore
Click to expand...
Click to collapse
Thanks for your advice, but I live in France, and there is no Verizon store here.

Your options now are:
1) Try flashing the System.img I uploaded, it might work, it might not
2) Wait until a full fastboot image comes out and then flash that.

Lum_UK said:
Your options now are:
1) Try flashing the System.img I uploaded, it might work, it might not
2) Wait until a full fastboot image comes out and then flash that.
Click to expand...
Click to collapse
Well, i flashed the system.img (thanks a lot for the update btw), and now the phone boots on AP Fastboot with "(boot failure), with at the botom of the screen i've got these line :
"Invalid CG OTV (CG:system): Invalid SP Data
Invalid CG HAB (CG:system, status: 0X0056)
Invalid CG OTV (CG:system)"

Lightofdark said:
Well, i flashed the system.img (thanks a lot for the update btw), and now the phone boots on AP Fastboot with "(boot failure), and a the botom of the screen i've got these line :
"Invalid CG OTV (CG:system): Invalid SP Data
Invalid CG HAB (CG:system, status: 0X0056)
Invalid CG OTV (CG:system)"
Click to expand...
Click to collapse
Well it was worth a try. Now you'll just have to turn it off and hope the fastboot files show up soon

ok, so I'll wait. Anyway, thanks a lot for your help and your time.

Hello,
I was lead here because I'm having a similar problem... though not nearly as bad as the OP, it would seem. I managed to brick my system partition by trying to restore a nandroid of a working JB system partition in safestrap to stock slot to resolve some other errors in the install precipitated by a bad restore from Titanium.
Good news is that safestrap still works, and I can boot to any other slot... just not stock. When trying to boot stock, after the safestrap screen, I just get a black screen... it makes the *droid* sound, but screen stays black and nothing happens. No logo or OS appears.
I'm wondering if it might be worth a try to flash your system.img, or if I should leave it alone and run on safestrap until fastboots show up (which is hopefully soon)?
Thanks!

[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5

How to flash a factory image | Return to stock | Unroot your Nexus 5​
Hello Nexus 5 Users!
I see many users that don't know how to restore their Nexus 5 to stock. It may come in handy, either when you want to RMA your phone, or you want to fix your mistakes.
This process consists of wiping and flashing every partition on your phone.​
{
"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"
}
WARNING!!!
This process will wipe your phone completely. Backup your storage before you continue.
I am also not responsible if anything goes wrong.
You can backup apps and data using this app before you unlock the bootloader. No root required.
https://play.google.com/store/apps/details?id=com.koushikdutta.backup
DO NOT USE TOOLKITS!!!
They have a high probability of something going wrong if you don't know how to use them (which, if you managed to ruin your phone, probably is true).
I don't mean to offend toolkit creators. They did a great job. But don't risk bricking your phone just because you're lazy.
FOLLOW EVERY SINGLE STEP
or you will end up in a bootloop, or with a bricked phone, and we don't want that
Let's get started!!
Setting up​
For this process, you will need to:
★Install adb and fastboot drivers. To do this, use this simple program:
http://forum.xda-developers.com/showthread.php?t=2588979
For MAC users:
http://forum.xda-developers.com/showthread.php?t=1917237
*Note: MAC users will have to write "./" before every command in this thread. For example : "./fastboot flash recovery recovery.img"
Linux users should know their stuff
http://forum.xda-developers.com/showthread.php?t=921169
★Download the latest factory images from here:
https://developers.google.com/android/nexus/images#hammerhead
★Extract the archive you downloaded (Use WinRAR). It should look like this:
★Unlock your bootloader (In case you haven't already)
http://forum.xda-developers.com/showthread.php?t=2507905
Flashing the factory images​
There is more than one way to flash these images. Each give the same results, but the first is for lazy users
Method 1. Easy method.
★Power off your phone.
★Boot it in fastboot by pressing and holding Power Button + Volume Down at the same time.
★Connect your phone to your PC through your USB cable.
★Execute the flash-all.bat script (for Windows) or flash-all.sh(for MAC and LINUX) in the folder where you extracted the factory images.
**!!** For MAC: You'll have to edit the flash-all.sh, and add "./" before every fastboot command.
★Wait for everything to flash.
★After everything finished, select "Recovery" using the volume buttons.
★When a small dead Android appears, press Power Button + Volume UP.
★Select "Wipe data/factory data reset"
★Reboot. Your phone should be stock. :good:
Method 2. Long method (Same thing actually, but I'll mention it, just in case)
★Extract the image-hammerhead-krt16m.zip somewhere easy to access (On C:\image-hammerhead-krt16m for example). You will have the following files:
★In the same folder, from the original archive, extract "bootloader-hammerhead-XXXXXX.img" (rename it to bootloader.img) and "radio-hammerhead-XXXXXX.img" (rename it to radio.img)
★Power off your phone.
★Boot it in fastboot by pressing and holding Power Button + Volume Down at the same time.
★Connect your phone to your PC through your USB cable.
★Open a CMD window.
★Type the following commands, in this order (If you have a different folder, change the path)
Code:
fastboot flash bootloader C:\image-hammerhead-krt16m\bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:\image-hammerhead-krt16m\radio.img
fastboot reboot-bootloader
fastboot flash system C:\image-hammerhead-krt16m\system.img
fastboot flash userdata C:\image-hammerhead-krt16m\userdata.img
[B](Note: this command will wipe your device (including \sdcard), EVEN if your bootloader is already unlocked.)[/B]
fastboot flash boot C:\image-hammerhead-krt16m\boot.img
fastboot flash recovery C:\image-hammerhead-krt16m\recovery.img
fastboot erase cache
fastboot flash cache C:\androidimage\cache.img
★After everything finished, select "Recovery" using the volume buttons.
★When a small Android appears, press Power Button + Volume UP.
★Select "Wipe data/factory data reset"
★Reboot. Your phone should be stock. :good:
For both methods:
Optional, but necessary for warranty purposes - Locking your bootloader+ Resetting the tamper flag
The Nexus 5 has a thing implemented in the bootloader called a tamper flag. This shows if the bootloader was ever unlocked, kind of like the flash counter with Samsung devices. You can check it out by using this command
Code:
fastboot oem device-info
. If the tamper flag value is "true", then you'll have to reset it. The following steps will reset this flag, and lock your bootloader.
•So, first, go here: http://forum.xda-developers.com/showthread.php?t=2239421 (Thanks @osm0sis for the wonderful script)
Under "Flashable Zips", you will find the Nexus BootUnlocker script. Download it.
•Put the zip on your internal storage.
•Download the latest TWRP recovery image for the Nexus 5 from here: http://techerrata.com/browse/twrp2/hammerhead. Rename it to TWRP.img.
Now boot it. You do this by booting your phone in fastboot, and typing the following command:
Code:
fastboot boot path\to\TWRP.img
*Replace path\to\TWRP.img with the path to where you placed the TWRP.img. For example: C:\Users\X\Desktop\TWRP.img
TWRP recovery should boot.
•When TWRP finished booting, select "Install", then navigate to the Nexus Bootunlocker zip, select and install it. After it finished, use the back arrow at the bottom of the screen to go back, and reboot.
Now your bootloader should be locked, and your tamper flag should show "false".
And now you have a brand new Nexus 5 (software wise, at least)​​
Video Guides​
Thanks @techfanatic9.
For Windows:
For Mac:
Another easy and fast tutorial made by @iTzGavin96
These don't contain the tamper flag reset step. Follow the steps above to reset your tamper flag value to "False" for warranty purposes.
If you now have 12 GB of storage instead of 28 GB, go to post #2​

32 GB phone now shows 16GB?​
This is a common problem with Nexus devices. Minor error, don't panic. Here is how to fix it
★Boot into STOCK RECOVERY (If you are running a custom recovery you must flash to stock)
★Clear cache
★Factory reset
If that didn't work, proceed with doing this:
Open a CMD window, boot your phone is fastboot, and write the following commands, in this order (Considering that you have extracted the images in C:\image-hammerhead-krt16m\)
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader C:\image-hammerhead-krt16m\bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:\image-hammerhead-krt16m\radio.img
fastboot reboot-bootloader
fastboot flash system C:\image-hammerhead-krt16m\system.img
fastboot flash userdata C:\image-hammerhead-krt16m\userdata.img
(Note: this command will wipe your device (including \sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:\image-hammerhead-krt16m\boot.img
fastboot flash recovery C:\image-hammerhead-krt16m\recovery.img

Credits and Thanks:
@efrant
For his thread in the N4 section (http://forum.xda-developers.com/showthread.php?t=2010312)
@osm0sis
For contributing a lot with the tamper flag part
@dombera
For inspiring me to make this guide
@Chromium_
For not replying to my Hangouts messages
@jd1639
For helping me out with this thread.
@Prodeje79
For pointing problems out.
​

abaaaabbbb63 said:
Chromium_
For not replying to my Hangouts messages
Click to expand...
Click to collapse
I do my best
Jk, my school has WiFi jammers in some of the classes.
Sent using xda-developers app

Chromium_ said:
I do my best
Jk, my school has WiFi jammers in some of the classes.
Sent using xda-developers app
Click to expand...
Click to collapse
Really? That's..... evil!!

abaaaabbbb63 said:
Really? That's..... evil!!
Click to expand...
Click to collapse
Evil...more like illegal.

Bleah.. The Dotted divider looks horrible on Tapatalk....
Meh

Because I don't know better, why do you consider method 2 safer?

Is there an easier "hide root" or any way to unroot where AirwatchMDM or other MDM corporate software control crap is hidden?
I'm wanting to try register on airwatch then lock down airwatch and see if I could still use touchdown.

jd1639 said:
Because I don't know better, why do you consider method 2 safer?
Click to expand...
Click to collapse
Well, safer in the sense that you are more in control, and can only flash certain images, not all. I'll delete de safe part.
fintheman said:
Is there an easier "hide root" or any way to unroot where AirwatchMDM or other MDM corporate software control crap is hidden?
I'm wanting to try register on airwatch then lock down airwatch and see if I could still use touchdown.
Click to expand...
Click to collapse
If you have root through the "SuperSU" app, it has an unroot option.

My keeps boot looping

sergiox209 said:
My keeps boot looping
Click to expand...
Click to collapse
Did you factory reset from the Stock Recovery?

abaaaabbbb63 said:
Did you factory reset from the Stock Recovery?
Click to expand...
Click to collapse
not the stock one a Rom

sergiox209 said:
not the stock one a Rom
Click to expand...
Click to collapse
Wait, what exactly did you do?

abaaaabbbb63 said:
Wait, what exactly did you do?
Click to expand...
Click to collapse
honestly i forgot but it keeps telling me in CMW error mounting /data if i try to wipe data

sergiox209 said:
honestly i forgot but it keeps telling me in CMW error mounting /data if i try to wipe data
Click to expand...
Click to collapse
You flashed CWM without booting in the stock ROM?
Please, follow the guide accordingly.
Try keeping it stock for the first boot. Then, you may install a custom recovery.

abaaaabbbb63 said:
You flashed CWM without booting in the stock ROM?
Please, follow the guide accordingly.
Try keeping it stock for the first boot. Then, you may install a custom recovery.
Click to expand...
Click to collapse
yes thats what im trying to do but it keeps boot looping. if there a way i can fix?

sergiox209 said:
yes thats what im trying to do but it keeps boot looping. if there a way i can fix?
Click to expand...
Click to collapse
The bootloop is most probably caused by you not factory resetting. Do you have the stock recovery right now?

abaaaabbbb63 said:
The bootloop is most probably caused by you not factory resetting. Do you have the stock recovery right now?
Click to expand...
Click to collapse
the file that you provide i have that download.

sergiox209 said:
the file that you provide i have that download.
Click to expand...
Click to collapse
Ok, so you installed using the flash-all.bat? Then you have stock recovery.
In bootloader, select "Recovery". When the small Android comes up, press Power Button + Volume UP. From the menu, select "wipe data/factory reset"

[Q] Boot-Up Issue, Unrooted, Please help

Woke up today after using my phone to set an alarm last night...and my phone was shutdown (plugged in).
I tried starting it up, and the phone wouldn't boot past the white HTC startup screen. Since then I've tried booting up several times, including using volume down button, and then clicking fastboot, but the screen just goes black and nothing happens. Effectively I'm stuck at the start-up screen.
My phone is only a couple months old, and is not rooted. Also since I have not attempted anything fancy, I have not yet backed up any of my data, photos, etc. The only advice I've had so far is to do a factory reset, but this would erase important videos, which I really don't want to loose.
Does anyone have suggestions on things to try to either somehow backup my data before a reset, or to fix this issue?
Thanks,
Bill

billiam864 said:
Woke up today after using my phone to set an alarm last night...and my phone was shutdown (plugged in).
I tried starting it up, and the phone wouldn't boot past the white HTC startup screen. Since then I've tried booting up several times, including using volume down button, and then clicking fastboot, but the screen just goes black and nothing happens. Effectively I'm stuck at the start-up screen.
My phone is only a couple months old, and is not rooted. Also since I have not attempted anything fancy, I have not yet backed up any of my data, photos, etc. The only advice I've had so far is to do a factory reset, but this would erase important videos, which I really don't want to loose.
Does anyone have suggestions on things to try to either somehow backup my data before a reset, or to fix this issue?
Thanks,
Bill
Click to expand...
Click to collapse
Maybe you should try to erase cache and reboot?
Code:
fastboot erase cache
fastboot reboot

alray said:
Maybe you should try to erase cache and reboot?
Code:
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
I am noob at this. my phone is unrooted, so my bootloader is locked. How do I run the erase cache command as you suggested? I've spent sometime looking for a forum telling me how, but have not found anyting... presumably i need software for my pc and connect the phone to it, or should there be some menu on the phone i can get to, to type in the command?

billiam864 said:
I am noob at this. my phone is unrooted, so my bootloader is locked. How do I run the erase cache command as you suggested? I've spent sometime looking for a forum telling me how, but have not found anyting... presumably i need software for my pc and connect the phone to it, or should there be some menu on the phone i can get to, to type in the command?
Click to expand...
Click to collapse
you will need to have fastboot/adb tools installed on your computer ----> HERE
and you'll need latest HTC drivers installed. This can be done by installing HTC sync software you can find HERE
start with this, ill update this post with more instructions
reboot phone in bootloader mode (hold down POWER + VOL DWN)
you will have a screen similar to 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"
}
select ''FASTBOOT'' (use volume up/down to navigate and power button to select)
then connect phone to computer (better to use a usb port at the back of your computer and don't use any usb hub)
The screen should now display ''FASTBOOT USB''' and the phone should be recognized by your computer.
Now open adb/fastboot tool by clicking on ''Minimal ADB and Fastboot'' icon
it will open a cmd prompt like this:
type these cmds:
Code:
fastboot erase cache [COLOR="Red"]<------- press ''enter''[/COLOR]
fastboot reboot [COLOR="red"]<------- press ''enter''[/COLOR]
now the phone will reboot
check if the phone is now booting properly.
btw no need to unlock the bootloader and root your phone atm

alray said:
you will need to have fastboot/adb tools installed on your computer ----> HERE
and you'll need latest HTC drivers installed. This can be done by installing HTC sync software you can find HERE
start with this, ill update this post with more instructions
reboot phone in bootloader mode (hold down POWER + VOL DWN)
you will have a screen similar to this
select ''FASTBOOT'' (use volume up/down to navigate and power button to select)
then connect phone to computer (better to use a usb port at the back of your computer and don't use any usb hub)
The screen should now display ''FASTBOOT USB''' and the phone should be recognized by your computer.
Now open adb/fastboot tool by clicking on ''Minimal ADB and Fastboot'' icon
it will open a cmd prompt like this:
type these cmds:
Code:
fastboot erase cache [COLOR="Red"]<------- press ''enter''[/COLOR]
fastboot reboot [COLOR="red"]<------- press ''enter''[/COLOR]
now the phone will reboot
check if the phone is now booting properly.
btw no need to unlock the bootloader and root your phone atm
Click to expand...
Click to collapse
Ok,
so i installed the ADB command prompt and the HTC Sync program.
Booted up my phone and got the Fastboot USB indicator...typed in the first command and received an error. (see attached image).

billiam864 said:
Ok,
so i installed the ADB command prompt and the HTC Sync program.
Booted up my phone and got the Fastboot USB indicator...typed in the first command and received an error. (see attached image).
Click to expand...
Click to collapse
the phone is recognised by the computer?
what is the ouput of
Code:
fastboot devices
?

alray said:
the phone is recognised by the computer?
what is the ouput of
Code:
fastboot devices
?
Click to expand...
Click to collapse
My result was: FA38VS902912 fastboot
Seems like the computer sees the Phone...

billiam864 said:
My result was: FA38VS902912 fastboot
Seems like the computer sees the Phone...
Click to expand...
Click to collapse
Yes phone is correctly recognized. Honestly its the first time I see that ''erasing error''.
You might want to try factory reset your phone... but it will wipe all your data.
Your phone is only a couple months old... still under warranty?
Btw factory reset is step #1 when you call htc cus.ser.

alray said:
Yes phone is correctly recognized. Honestly its the first time I see that ''erasing error''.
You might want to try factory reset your phone... but it will wipe all your data.
Your phone is only a couple months old... still under warranty?
Btw factory reset is step #1 when you call htc cus.ser.
Click to expand...
Click to collapse
Okay, well thanks for trying... was really hoping to keep my videos and photos... If you think of anything please repost!

Factory reset should NOT wipe sdcard. But I don't have a htc one to test right bow
sent from my mobile device

billiam864 said:
Okay, well thanks for trying... was really hoping to keep my videos and photos... If you think of anything please repost!
Click to expand...
Click to collapse
yes as @SaHiLzZ said, factory reset won't wipe the internal sdcard partition where your photo and video are stored. It will wipe /data partition where your users settings and app are stored. so you should not lost your media files.
The other options will require unlocking bootloader which will void your warranty. So if your phone is still under warranty better to get it repaired or replaced instead.

alray said:
yes as @SaHiLzZ said, factory reset won't wipe the internal sdcard partition where your photo and video are stored. It will wipe /data partition where your users settings and app are stored. so you should not lost your media files.
The other options will require unlocking bootloader which will void your warranty. So if your phone is still under warranty better to get it repaired or replaced instead.
Click to expand...
Click to collapse
Also unlocking bootloader at HTCDEV will wipe the phone totally / sdcard and all

clsA said:
Also unlocking bootloader at HTCDEV will wipe the phone totally / sdcard and all
Click to expand...
Click to collapse
I hope you all are correct. I spoke with HTC about sending in my phone for repair, and they said that since HTC One phones don't have an external or removal SD card...just internal memory, that all my photos/files/etc will be lost in the factory reset. Perhaps this discrepancy is in the model or type of HTC One?
Thanks,

Can't unlock OEM Bootloader on officially unlocked Redmi 4X Santoni 16GB

Dear Reader,
As you could see on a video, the device is unlocked using official method ( SMS ), but after when trying to unlock the OEM bootloader it locks itself again.
Why and how to unlock it completely to flash TWRP and Root ?
Thank you.
Best regards,
V7

its already unlocked. try to flash twrp maybe? as you can see the bootloader is already unlocked, then you can flash custom recovery
why are you confused? the settings app already told you its already unlocked

Exodus4 said:
its already unlocked. try to flash twrp maybe? as you can see the bootloader is already unlocked, then you can flash custom recovery
why are you confused? the settings app already told you its already unlocked
Click to expand...
Click to collapse
Thank you for your reply, really.
As you could notice, the trigger sets itself to disabled when menu changes( it doesn't stay at its position ), so I though that the trigger just doesn't work, doesn't it ?

There is only ONE bootloader. You already unlocked it. That trigger is only for enabling lock and unlock from fastboot interface using the code "fastboot oem unlock", which many other android devices use, but probably not for xiaomi ones. That trigger is NOT for unlocking bootloader, or in other words, turning it on DOES NOT unlock the bootloader. There is no such thing as "OEM bootloader". Your bootloader is already unlocked. Go to fastboot and flash TWRP and do whatever you want.

NTLinhHaHa said:
There is only ONE bootloader. You already unlocked it. That trigger is only for enabling lock and unlock from fastboot interface using the code "fastboot oem unlock", which many other android devices use, but probably not for xiaomi ones. That trigger is NOT for unlocking bootloader, or in other words, turning it on DOES NOT unlock the bootloader. There is no such thing as "OEM bootloader". Your bootloader is already unlocked. Go to fastboot and flash TWRP and do whatever you want.
Click to expand...
Click to collapse
Thank you for your reply really.
By the way, I've already tried to flash a custom recovery like TWRP 3.2.1.0, but after rebooting into recovery the old recovery had been shown, even if fastboot tells that everything regarding flashing is OK, so I though it's just locked. Do you know why it loads old stock recovery ?

vv7v7 said:
Thank you for your reply really.
By the way, I've already tried to flash a custom recovery like TWRP 3.2.1.0, but after rebooting into recovery the old recovery had been shown, even if fastboot tells that everything regarding flashing is OK, so I though it's just locked. Do you know why it loads old stock recovery ?
Click to expand...
Click to collapse
Is it really the old recovery, or just a screen with a bunch of yellow buttons? If it's the latter, did you try touching the "recovery" button and THEN the left-side button (there will be a blue and a green button shown)?
After that the phone will boot twrp.
If it's really the old recovery, how did you flash twrp? Through adb? Did you try just booting twrp instead of flashing it? Like "fastboot boot twrp.img" ?

NTLinhHaHa said:
Is it really the old recovery, or just a screen with a bunch of yellow buttons? If it's the latter, did you try touching the "recovery" button and THEN the left-side button (there will be a blue and a green button shown)?
After that the phone will boot twrp.
If it's really the old recovery, how did you flash twrp? Through adb? Did you try just booting twrp instead of flashing it? Like "fastboot boot twrp.img" ?
Click to expand...
Click to collapse
Thank you for your reply really.
Yes, I've used adb and did everything like in this article ( where "Install via ADB" ). So, after that, when clicked on "recovery" ( in menu like you've described above ) it asked me something like "Am I sure to proceed ?", so I accepted this one with a blue button "OK" and it went to "MI-Recovery 3.0" like:
{
"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"
}
( image's from internet )

vv7v7 said:
Thank you for your reply really.
Yes, I've used adb and did everything like in this article ( where "Install via ADB" ). So, after that, when clicking on "recovery" and accepting with blue button "OK" it goes to "MI-Recovery 3.0" and shows:
( image's from internet )
Click to expand...
Click to collapse
While "installing via ADB", did your phone actually rebooted into Fastboot mode? (the screen showing an android and the word "FASTBOOT" on it)
Try it this way: while the phone is on, reboot the phone via power menu. When the Mi logo appears and the device vibrates a bit, start holding both "Power" button and "Volume down" button (Vol-) until the phone vibrates again. Release both buttons. THEN plug the phone to PC, open adb command prompt window. Assuming the twrp image on your computer is named twrp3210.img, here's the code you need to enter:
Code:
fastboot flash recovery twrp3210.img
After that, go to recovery like you normally do.
That should work.
Remember from now on: Power + Vol- = Fastboot; Power + Vol+ = Recovery. You cannot go to recovery or bootloader from adb in MIUI stock rom.

NTLinhHaHa said:
While "installing via ADB", did your phone actually rebooted into Fastboot mode? (the screen showing an android and the word "FASTBOOT" on it)
Try it this way: while the phone is on, reboot the phone via power menu. When the Mi logo appears and the device vibrates a bit, start holding both "Power" button and "Volume down" button (Vol-) until the phone vibrates again. Release both buttons. THEN plug the phone to PC, open adb command prompt window. Assuming the twrp image on your computer is named twrp3210.img, here's the code you need to enter:
Code:
fastboot flash recovery twrp3210.img
After that, go to recovery like you normally do.
That should work.
Remember from now on: Power + Vol- = Fastboot; Power + Vol+ = Recovery. You cannot go to recovery or bootloader from adb in MIUI stock rom.
Click to expand...
Click to collapse
Thank you.
So, I've done the same as you described:
The "fastboot" text was show with a rabbit like
( image's from internet ), so after I've executed the command:
Code:
fastboot flash recovery twrp3210.img
it shows something like:
( image's from internet ) and after just turned off the phone. Then I've pressed Power + Vol+ and it shows the chinese menu like:
( image's from internet )

vv7v7 said:
Thank you.
So, I've done the same as you described
Click to expand...
Click to collapse
Yes, and then press recovery and then the left-side button.

NTLinhHaHa said:
Yes, and then press recovery and then the left-side button.
Click to expand...
Click to collapse
Thank you.
As you could notice from previous messages
So, after that, when clicked on "recovery" ( in menu like you've described above ) it asked me something like "Am I sure to proceed ?", so I accepted this one with a blue button "OK" and it went to "MI-Recovery 3.0" like:
Click to expand...
Click to collapse
already done this one and got stock recovery.

vv7v7 said:
Thank you.
As you could notice from previous messages already done this one and got stock recovery.
Click to expand...
Click to collapse
How about typing into fastboot:
Code:
fastboot oem device-info
Does the returned message say that you are unlocked?
How about trying a different twrp image?

NTLinhHaHa said:
How about typing into fastboot:
Code:
fastboot oem device-info
Does the returned message say that you are unlocked?
How about trying a different twrp image?
Click to expand...
Click to collapse
Thank you.
The command above gave:
Code:
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.005s]
finished. total time: 0.005s
I've tried to boot into TWRP with "fastboot boot twrp.img" exactly after flashing "twrp.img", so it booted into TWRP normally, but after reboot into bootloader and choose a recovery it booted into stock rom recovery as before.
Old TWRP versions don't have some features which has 3.2.1.0, so it's rather interesting why this one doesn't boot after flashing and rebooting.
Although, there's a chance that stock rom reflashes recovery each reboot, so that's why. What do you think, is it possible ?

vv7v7 said:
Thank you.
The command above gave:
Code:
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.005s]
finished. total time: 0.005s
I've tried to boot into TWRP with "fastboot boot twrp.img" exactly after flashing "twrp.img", so it booted into TWRP normally, but after reboot into bootloader and choose a recovery it booted into stock rom recovery as before.
Old TWRP versions don't have some features which has 3.2.1.0, so it's rather interesting why this one doesn't boot after flashing and rebooting.
Although, there's a chance that stock rom reflashes recovery each reboot, so that's why. What do you think, is it possible ?
Click to expand...
Click to collapse
You can totally see from the returned message that your device is unlocked. Yes, and possibly stock rom reflashes recovery each boot. So your way should be to boot twrp.img, wipe System, Data and all caches. install a new rom, and then reboot to fastboot to flash twrp.img into recovery =)))

NTLinhHaHa said:
You can totally see from the returned message that your device is unlocked. Yes, and possibly stock rom reflashes recovery each boot. So your way should be to boot twrp.img, wipe System, Data and all caches. install a new rom, and then reboot to fastboot to flash twrp.img into recovery =)))
Click to expand...
Click to collapse
Thank you.
By the way, in case of leaving stock rom on board and wiping Data and Caches will turn rom to factory reset, but will leave it, is it right ?

vv7v7 said:
Thank you.
By the way, in case of leaving stock rom on board and wiping Data and Caches will turn rom to factory reset, but will leave it, is it right ?
Click to expand...
Click to collapse
Yeah, wipe data + cache = factory reset

Mi A2 - Failed to boot - after system update

Hello everyone, yesterday morning, Sunday 12/15/19, the system message "restart the device to make the system update effective".
So I do as I have always been.
The phone, an Mi A2, goes into bootloop and then a white screen appears on a black background with the title:
"<!> Failed to boot"
"Press the Volume keys to select then the Power button to continue.
RETRY
POWER OFF "
Choosing "RETRY" verifies bootloop 3 or 4 times and then the recovery mode screen appears which says:
"Can't Load Android system. Your data may be corrupted. You should get the message you need to perform at factory data reset and erase all user data stored on this device."
It gives me the choice between:
-Try again
-Factory data reset
Choosing "Try again" returns the same routine as when "RETRY" is selected In the previous black background screen, bootloop and then the black background white screen described at the beginning.
I MUST ACCESS AND SAVE THE VERY IMPORTANT CONTENT. :crying:
I have all the photos and videos of my newborn daughter. I usually backup but this inconvenience suddenly caught me.
I surfed and I saw that many people found this problem after an update .. but I never found any solutions. I called the Xiaomi center in Novara indicated by the site but they told me that they only serve as a collection center to send to the assistance in the company Xiaomi, saying that the assistance resets the phone to restore its functioning and does not save the data. I tried to start the fastboot, the device is recognized by the PC and shows the locked bootloader. The program MiFlash asks me to start to install a set of drivers and then immediately generate an unhandled exception and crash.
Attached the images.
Can you help me? I do not know what to do..
{
"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 should try to use adb in recovery, if it works, you could digit "adb pull /sdcard".

Continue rebooting with external power on. Android One with A/B slots is supposed to reboot into previously (before OTA) active slot.

Aerobatic said:
Continue rebooting with external power on. Android One with A/B slots is supposed to reboot into previously (before OTA) active slot.
Click to expand...
Click to collapse
Thank you, can you explain me better what I should try to do?

HTCDevil said:
You should try to use adb in recovery, if it works, you could digit "adb pull /sdcard".
Click to expand...
Click to collapse
Is there any guide to do that?

pedrix82 said:
Is there any guide to do that?
Click to expand...
Click to collapse
I don't think so, when you are in recovery you should try to verify if your device is connected with "adb devices" and then you should use the command "adb pull /sdcard". But it usually works with custom recoveries, and if you have prevently enabled usb debugging.

pedrix82 said:
Thank you, can you explain me better what I should try to do?
Click to expand...
Click to collapse
First you can try to search this forum and read dozens of discussions of the same issue. Meanwhile you can plug in power adapter and reboot several times with pauses, probably sometimes switching to stock recovery and to fastboot mode, and then leave phone powered for a night.

HTCDevil said:
I don't think so, when you are in recovery you should try to verify if your device is connected with "adb devices" and then you should use the command "adb pull /sdcard". But it usually works with custom recoveries, and if you have prevently enabled usb debugging.
Click to expand...
Click to collapse
Thanks....I will try, I don't remember if I enabled the usb debugging mode, for sure I saw with fastboot that I have the bootloader Locked.

nothing to do...i tried ADB mode, but it is not enabled, only fastboot mode where i can do nothing because the bootloader is locked.
I also tried to install the Xiaomi tool, but it doesnt recognize the device.
i dont know what to do....

Did you try the factory data reset?

1N4148 said:
Did you try the factory data reset?
Click to expand...
Click to collapse
Hello...ehm...not, the aim is to recover all the data, photos and documents that are stored inside...

Same thing happened to me. You should manually switch the active partition in fastboot.

Zedsdeadbaby said:
Same thing happened to me. You should manually switch the active partition in fastboot.
Click to expand...
Click to collapse
Hi, I already tried to do what you suggest, but it is not possible with the bootloader Locked.
Anyway, can you tell me what I have to do to change the active partition? Maybe I don't do it as I should....

@pedrix82: I can only repeat, though you do not read and trust:
- the only (legal*) way to save data in bootloop with locked device is to boot;
- all other options are blocked for a locked Mi A2, - resetting, unlocking, etc. will erase user data; switching Slots and/or loading TWRP need unlocked phone; stock recovery is useless;
- Android One partitions system with A/B Slots was specifically designed to solve problems of failed OTAs, see https://source.android.com/devices/tech/ota/ab and https://android.googlesource.com/pl...ware/+/master/include/hardware/boot_control.h
Which means that: if you have bootloop after OTA on full stock (and have not tampered device yourself), after numerous attempts to boot -> the bootloader MUST detect that active Slot does not have bootable OS and MUST switch to the other Slot.
(non-legal*) - or read memory chip content at low-level and decipher encrypted data.

Aerobatic said:
@pedrix82: I can only repeat, though you do not read and trust:
- the only (legal*) way to save data in bootloop with locked device is to boot;
- all other options are blocked for a locked Mi A2, - resetting, unlocking, etc. will erase user data; switching Slots and/or loading TWRP need unlocked phone; stock recovery is useless;
- Android One partitions system with A/B Slots was specifically designed to solve problems of failed OTAs, see https://source.android.com/devices/tech/ota/ab and https://android.googlesource.com/pl...ware/+/master/include/hardware/boot_control.h
Which means that: if you have bootloop after OTA on full stock (and have not tampered device yourself), after numerous attempts to boot -> the bootloader MUST detect that active Slot does not have bootable OS and MUST switch to the other Slot.
(non-legal*) - or read memory chip content at low-level and decipher encrypted data.
Click to expand...
Click to collapse
Thanks,
It's really long time that I'm rebooting the mobile since it happened...
But cyclically and alternate I got the two image attached to the main post....

try a "fastboot continue" in adb

hello everyone, update.
unfortunately I was unable to recover anything and proceeded with the factory reset.
The phone has reset and everything is working.
So I thought to try to do a file recovery as you do for deleted files.
for the various recovery applications I need to root the device.
For this phone should be really simple but I'm still stuck in.
I followed one guide, then another, and then another .... all with the same procedures.
the result is that twrp recovery, if loaded with Vol + and pwr button hangs on the custom recovery logo.
I can only start the twrp recovery installed in the secondary partition of the phone.
but from this recovery, even if I install Magisk, with a successful results from the recovery, I do not root the device. I verified root with Magisk manager and rootchecker.
Help.... thanks

pedrix82 said:
... So I thought to try to do a file recovery as you do for deleted files.
Click to expand...
Click to collapse
I do no believe you'll be able to undelete files after factory reset.
pedrix82 said:
... for the various recovery applications I need to root the device. ... I followed one guide, then another, and then another .... all with the same procedures.
Click to expand...
Click to collapse
This guide works for everybody, except that
(1) there is obsolete "fastboot oem unlock" command stated which should better be changed to "fastboot flashing unlock", and
(2) guide does not mention that each unlock step is to be approved on phone, and
(3) guide skips step of patching stock boot.img in phone with MagiskManager, - while exactly this step creates archived copy of stock boot image in /data root, thus allowing to restore images (actually restoring stock boot image) before downloading next OTA, and
(4) only 1st variant - that is booting into patched boot image and then making "Direct Install" is safe - it allows to check that patched boot image is suitable for ROM.
pedrix82 said:
...the result is that twrp recovery, if loaded with Vol + and pwr button hangs on the custom recovery logo.
I can only start the twrp recovery installed in the secondary partition of the phone....
Click to expand...
Click to collapse
IMHO that just means that you did not do your homework (I mean you have not read guides and discussions and Google info with links I provided) well enough to understand that with A/B slots partitions structure there is no separate /recovery partition in phone (instead, recovery is embedded into /boot image), and thus we cannot just "flash TWRP" into MiA2.
Instead, TWRP can only be embedded into boot image (patching previously flashed suitable boot image), which is made by installing TWRP.zip in temporarily booted TWRP.img. Thus, if you want to have both root and permanent TWRP (I still do not see why anybody needs permanent TWRP with rooted stock), first get root with patched boot image, and then install TWRP patching this Magisk-patched boot image once more.
And I do think that "TWRP 4pda edition" is working better than so called "official TWRP".

Found the solution,
First u need to get to the recovery menu by pressing vol up + power, tap it multiple times after retry boot...you have to be quick...and eventually will get to the android robot pic with "no command"....keep pressing till you get to the full recovery menu. (this might take multiple tries)
Then go to update using adb. (you need all the files for adb, usb drivers, latest mi a2 update zip, you can find tutorials in youtube/google )
after updating it should boot up fine with all data intact.
If latest update versions dont boot, try repeating will older version.
Make sure you backup everthing afterwards! and enable oem unlocking &usb debugging for potential future issues.
Hope this helps!