galaxy nexus i9250, bootloops, impossible flash it, how to check hardware status? - Samsung Galaxy Nexus

problem: bootloops, impossible to recovery/install recovery/rom/flash
model: samsung galaxy nexus gt-i9250
bootoloader: locked (unlocked by fastboot just for follow tests)
rom: factory stock original 4.3 JB (JWR66Y)
USB debub: disable (impossible to disable in bootloop)
Developer option: disable (impossible to disable in bootloop)
smartphone boot loop (really it loads android, but reboots randomly after a few second explecially if i try to use it immediately )
in fastboot mode/recovery mode/downloading mode smartphone don' have a bootloop
i tried to reset by different ways:
1) "flash stock + unroot " (soft-bricked/bootloop ) by "nexus root toolkit" , all operation complete correctly but after that , when i restart a phone , it start in the same condition before the reset. i try to use different image (factory image/cyanogenmod /clockworkmod ), same result
2) flash with utility fastboot in fastboot mode and install differente image
3) flash with utility adb in adb mode and install differente image
4) reset with odin utility in downloading mode and install differente image
all operation (erase/sending/write ) complete, but really when start a phone it come back to initial condition.
PS: i try to make any simple operation during system is up and before it have bootloop, but it don't save never, I fear not able to write nothing in all mode
PS2: i try olso to "erase all nand" with odin, and in this condition i recived a "write error" (differt in a normal reset i don't have this error)
it's possible that my NAND is coocked? it's possible to test it in my condition? how to check hardware status? i must change all system board? or all smartphone ?
thanks

Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Register an account on XDA to have full acces on site.
Stand by
Good luck

Related

[SOLVED] ZE550ML bricked after Marshmallow Beta - Now fastboot but no more serial no

Hello everyone, I've been trying to unbrick my ZenFone 2 ZE550ML for at least 5 hours...
(first, the small history...)
I've a french ASUS ZenFone 2 ZE550ML (Z008D) with 2 Go of RAM running latest Lollipop official ROM (I never unlocked bootloader or rooted it)
I suscribed to Asus beta tester program on ZenTalk forum, so I received the Marshmallow upgrade via official OTA last night.
Everything updated normally, I had enough space, update has been completed, I saw the ASUS logo on dark background because it's not unlocked, I saw the message "Optimizing apps..."(ART compiling)... and I successfully booted to Marshmallow... but just one time.
What happened is that my ZenFone 2 is... really... slow... and... with... Marshmallow... it... had... the... same.... slowness... than... with... Lollipop :silly:
And, after playing around with Marshmallow around ten minutes (apps were updating through Play Store), my phone hung, only because of slowness. I could make it sleep (screen turning on/off, that's all, no lock screen), and I could just access to shutdown/reboot menu if I press 3 seconds the Power button. But it was frozen, like it often did in Lollipop.
I waited 15 minutes, because I thought turning off while updating apps like Google Play Services was not a brilliant idea. After 15 minutes of waiting, still frozen, but even more frozen : no power menu, and orange LED was still ON even after disconnecting the charger. I decided to reset my ZenFone 2 by pressing power button 10 seconds.
And... I rebooted it => vibration, then immediately USB logo (when POWER or POWER+UP VOLUME). Nothing more after that. No LED while charging (if I plug it to a charger, it boot loop with USB logo). It's very frustrating because... I saw ASUS logo just before optimization, and I stopped it AFTER update, not during :crying:
(now what I tried)
Today I tried to apply this guide : http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
I managed to install every driver, I downloaded every file/image I could...
Because of USB logo, my device is always recognized as a Moorefield device with known driver
Following the guide, I sent to my phone the basic 4-coulour bootloader using xFSTK, no problem
Here is the problem now : I've a working fastboot menu, fastboot is recognized by my computer, BUT almost every fastboot command fails, because my serial number was set to 0123456789ABCDEF :crying:
-> Fastboot error is systematically : FAILED (remote: flash_cmds error! (this happens after successfully downloading to phone, but it's not applying)
and, I tried "fastboot erase cache" :
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (status read failed (Too many links))
I never had any software mess in my phone :crying:
So I don't know what to do, because I would like to flash only splashscreen, recovery and boot if possible, I don't want to lose data
I'm actually downloading a RAW for WW_ZE550ML_2.20.40.149 that I'll sideload with Asus Flash Tool (without wiping data) if it's the only way to do
Where can I find working images for fastboot that can be flashed on a generic serial number?
Thanks for your answers
Edit 1 : OH WAIT... The fastboot screen on my ZenFone 2 Z008 says :
PRODUCT_NAME - Z00A
VARIANT - ASUS_Z00A
WTF ASUS ?!?!?!?!
The ONLY things I did are : OTA update to Marshmallow (I never had OTA issues before) and sending through xFSTK the FW DNx, IFWI and OS Images FOR ZE550ML given in the guide... What happened?! Please please please, can somebody give me the right files? Thank you ^^
(sorry for eventual bad english, I'm a tired french)
Have you tried to re flash fastboot (fastboot flash droidboot.img)?
About the serial number, I think 0123..DEF is normal because I mine is like yours, too. But everything is fine.
fanfan54 said:
Hello everyone, I've been trying to unbrick my ZenFone 2 ZE550ML for at least 5 hours...
(first, the small history...)
I've a french ASUS ZenFone 2 ZE550ML (Z008D) with 2 Go of RAM running latest Lollipop official ROM (I never unlocked bootloader or rooted it)
I suscribed to Asus beta tester program on ZenTalk forum, so I received the Marshmallow upgrade via official OTA last night.
Everything updated normally, I had enough space, update has been completed, I saw the ASUS logo on dark background because it's not unlocked, I saw the message "Optimizing apps..."(ART compiling)... and I successfully booted to Marshmallow... but just one time.
What happened is that my ZenFone 2 is... really... slow... and... with... Marshmallow... it... had... the... same.... slowness... than... with... Lollipop :silly:
And, after playing around with Marshmallow around ten minutes (apps were updating through Play Store), my phone hung, only because of slowness. I could make it sleep (screen turning on/off, that's all, no lock screen), and I could just access to shutdown/reboot menu if I press 3 seconds the Power button. But it was frozen, like it often did in Lollipop.
I waited 15 minutes, because I thought turning off while updating apps like Google Play Services was not a brilliant idea. After 15 minutes of waiting, still frozen, but even more frozen : no power menu, and orange LED was still ON even after disconnecting the charger. I decided to reset my ZenFone 2 by pressing power button 10 seconds.
And... I rebooted it => vibration, then immediately USB logo (when POWER or POWER+UP VOLUME). Nothing more after that. No LED while charging (if I plug it to a charger, it boot loop with USB logo). It's very frustrating because... I saw ASUS logo just before optimization, and I stopped it AFTER update, not during :crying:
(now what I tried)
Today I tried to apply this guide : http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
I managed to install every driver, I downloaded every file/image I could...
Because of USB logo, my device is always recognized as a Moorefield device with known driver
Following the guide, I sent to my phone the basic 4-coulour bootloader using xFSTK, no problem
Here is the problem now : I've a working fastboot menu, fastboot is recognized by my computer, BUT almost every fastboot command fails, because my serial number was set to 0123456789ABCDEF :crying:
-> Fastboot error is systematically : FAILED (remote: flash_cmds error! (this happens after successfully downloading to phone, but it's not applying)
and, I tried "fastboot erase cache" :
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (status read failed (Too many links))
I never had any software mess in my phone :crying:
So I don't know what to do, because I would like to flash only splashscreen, recovery and boot if possible, I don't want to lose data
I'm actually downloading a RAW for WW_ZE550ML_2.20.40.149 that I'll sideload with Asus Flash Tool (without wiping data) if it's the only way to do
Where can I find working images for fastboot that can be flashed on a generic serial number?
Thanks for your answers
Edit 1 : OH WAIT... The fastboot screen on my ZenFone 2 Z008 says :
PRODUCT_NAME - Z00A
VARIANT - ASUS_Z00A
WTF ASUS ?!?!?!?!
The ONLY things I did are : OTA update to Marshmallow (I never had OTA issues before) and sending through xFSTK the FW DNx, IFWI and OS Images FOR ZE550ML given in the guide... What happened?! Please please please, can somebody give me the right files? Thank you ^^
(sorry for eventual bad english, I'm a tired french)
Click to expand...
Click to collapse
After flashing Z008 with xFSTK IAW the procedure you tried, the product name in fastboot screen is shown as ASUS_Z00A. After flashing with Asus flashtool, the fastboot screen says correct product number Z008 and corect serial number. :good:
I tried to flash boot.img, droidboot.img, system.img and recovery.img because I did not want to lose my data. Unfortunately, my Z008 did not accept the fastboot commands just like you, so I wiped my data. :crying:
It seems that this guy has succeeded to unbrick Z00A without losing his data. I have not tried this procedure in my Z008 using Z008 raw file yet, so I don't know if this is effective for Z008.
http://forum.xda-developers.com/showpost.php?p=67474121&postcount=210
Serial number restored by Asus Flash Tool, now I can flash with fastboot
Hakataben said:
After flashing Z008 with xFSTK IAW the procedure you tried, the product name in fastboot screen is shown as ASUS_Z00A. After flashing with Asus flashtool, the fastboot screen says correct product number Z008 and corect serial number. :good:
I tried to flash boot.img, droidboot.img, system.img and recovery.img because I did not want to lose my data. Unfortunately, my Z008 did not accept the fastboot commands just like you, so I wiped my data. :crying:
It seems that this guy has succeeded to unbrick Z00A without losing his data. I have not tried this procedure in my Z008 using Z008 raw file yet, so I don't know if this is effective for Z008.
http://forum.xda-developers.com/showpost.php?p=67474121&postcount=210
Click to expand...
Click to collapse
Hello,
Thanks for your answers
I let going Asus Flash Tool for 6 hours, I saw in the Task Manager and on my Zenfone that it used fastboot2 to erase partitions.
Phone said O.K
But it's stuck for 6 hours on a500cgfastboot (these files are here : C:\Program Files (x86)\ASUS\ASUS Flash Tool\Google)
So I think I'll have to reboot phone and PC and retry (I checked integrity of the raw with 7-zip (the raw file is actually a zip file which is unzipped in the folder %USERPROFILE%\.fbrawtempdir) but I'll re-download it...)
Maybe serial number just changed...
Edit after reboot : SO COOL
I discovered that a500cgfastboot was stuck because................................... by erasing some partions, fastboot2 restored the right serial number (I had to restart fastboot to see back my legit serial number)... and it restored product name to Z008
And because a500cgfastboot (and other command ran by Asus Flash Tool) have the old serial 0123456789ABCDEF for argument, a500cgfastboot was no longer finding my phone
I'll retry downloading my img files with fastboot... But I saw Asus Flash Tool cleaned system partition too, but I'll try...
Edit after flashing with fastboot
With the right serial number, everything flashed perfectly with fastboot (but there's one problem : in the Mega folder, there is not the system image for Marshmallow)
so, without system image, my phone boots (ASUS logo, etc...) BUT nothing happens after logo because fastboot2 wiped system :crying: :crying:
I have still access to Fastboot, like before bricking (POWER + VOL UP) (but I can't figure out how to enter in recovery, I've just the droid bot with exclamation mark)
(it's unbricked but no system)
fanfan54 said:
Hello,
Thanks for your answers
I let going Asus Flash Tool for 6 hours, I saw in the Task Manager and on my Zenfone that it used fastboot2 to erase partitions.
Phone said O.K
But it's stuck for 6 hours on a500cgfastboot (these files are here : C:\Program Files (x86)\ASUS\ASUS Flash Tool\Google)
So I think I'll have to reboot phone and PC and retry (I checked integrity of the raw with 7-zip (the raw file is actually a zip file which is unzipped in the folder %USERPROFILE%\.fbrawtempdir) but I'll re-download it...)
Maybe serial number just changed...
Edit after reboot : SO COOL
I discovered that a500cgfastboot was stuck because................................... by erasing some partions, fastboot2 restored the right serial number (I had to restart fastboot to see back my legit serial number)... and it restored product name to Z008
And because a500cgfastboot (and other command ran by Asus Flash Tool) have the old serial 0123456789ABCDEF for argument, a500cgfastboot was no longer finding my phone
I'll retry downloading my img files with fastboot... But I saw Asus Flash Tool cleaned system partition too, but I'll try...
Edit after flashing with fastboot
With the right serial number, everything flashed perfectly with fastboot (but there's one problem : in the Mega folder, there is not the system image for Marshmallow)
so, without system image, my phone boots (ASUS logo, etc...) BUT nothing happens after logo because fastboot2 wiped system :crying: :crying:
I have still access to Fastboot, like before bricking (POWER + VOL UP) (but I can't figure out how to enter in recovery, I've just the droid bot with exclamation mark)
(it's unbricked but no system)
Click to expand...
Click to collapse
If you want to use Marshmallow, I recommend to flash pre-rooted lollipop first, then to flash marshmallow. In your situation, you should unbrick your Z008 at first. After that, you can change system to Marshmallow easily.
Pre-rooted Z008 systems are here. http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
In my case, I needed to have rooted and bootloader-unlocked again to enter in recovery.
Yay!
ASUS Flash Tool flashed the 2.20.40.149 successfully
It's saying "Optimizing app 45 of 119", but I think I had 179 when upgrading to Marshmallow...
And my Android was in french before. But I think I'll be able to fix this
I'll check soon if I've still all my data and apps...
(also, I tried to film everything, if it works I could eventually upload a video tutorial )
Thanks
Another problem... Edit 1
Android boots, I haven't any installation "Welcome" popup because I did not reset it, but as a consequence it crashes at start :
"Unfortunately, android.process.media stopped"
"Unfortunately, android.process.acore stopped"
And it reboots
Maybe it's because these are Marshmallow apps... Will I have to reset it?
Or where can I find system.img for Marshmallow?
Edit 2 Just managed to access to recovery menu
Definitely solved
Solved without losing any data (except settings of some non-system apps)
Hello,
I found on ZenTalk (this thread : http://www.asus.com/zentalk/forum.php?mod=redirect&goto=findpost&ptid=78184&pid=392686) a working link to Latest Marshmallow sideload zip for ZE550ML OR ZE551ML. It was the right file, finally.
ZF2/ZE550ML/Z008/Android 6.0.1/WW-4.21.40.54 ~ download --> here.
ZF2/ZE551ML/Z00A/Android 6.0.1/WW-4.21.40.61 ~ download --> here.
Click to expand...
Click to collapse
I sideloaded this file using adb and recovery mode, it worked PER-FECT-LY : my phone just rebooted without any problem, like before the problem. And with latest Marshmallow obviously : I immediately received messages, could access to my pictures, apps, with the same settings than before, in French (just one thing: settings for some non-system apps are reset)
Here is guide of everything I did to unbrick a Marshmallow ZE550ML stuck on USB logo with no bootloader :
(Note: I recommend you to charge your ZenFone for a few hours as soon as you'll get fastboot menu at step 1, so it will not shutdown... Even if it's not turning on the orange LED, it's charging )
(Note also that these are the steps I had to do in order to unbrick MY phone without losing data and installing Marshmallow. For your phone some steps might be unnecessary, if you're lucky... I know this is a very long guide but I had to do this in MY case)
1. Flash basic bootloader with xFSTK Downloader to boot fastboot
I had, first, to switch to advanced startup with support for unsigned drivers (video tutorial here),
install Asus USB drivers (link to Asus USB drivers here - note: video tutorial to install drivers from inf (repeat for every device available : ADB Interface, Bootloader Interface, etc...) )
and IntelSocUSB driver (link to IntelSocUSB driver 1.2.0 - Note: Before finishing IntelSocUSB setup it will ask you to configure a device : you'll have to connect your ZenFone 2 using an USB cable to your computer, while it's displaying USB logo, and WAIT FOR DETECTION IN Device Manager as "Moorefield device" under "Intel Soc" section),
to flash a fastboot bootloader (link to xFSTK_ZE550ML-sal358-amtech.vn for ZE550ML / link to xFSTK_ZE551ML-sal358-amtech.vn for ZE551ML) using xFSTK Downloader (link to xFSTK Downloader 1.7.0) [B
(guides for everything in this step 1: english version - same in vietnamese with screenshots and valid links - detailed PDF for xFSTK with screenshots).[/B] => phone boots on fastboot
2. Flash a lollipop ROM (or Marshmallow raw if you find it) with Asus Flash Tool to repair fastboot info (like serial number) and access recovery if you want to install Marshmallow from a zip
In order to get a working recovery menu (because I found a zip for Marshmallow but no raw, I'll have to install a recovery),
I had to install Asus Flash Tool (link to Asus Flash Tool 1.14 - Note: archive password is www.asus-zenfone.com ),
flash a Lollipop raw (link to WW_ZE550ML_2.20.40.149.raw) on my ZenFone 2 ZE550ML using Asus Flash Tool (Model: ZE550ML - wipe data : no)
(guides for everything in this step 2: english version - same in vietnamese with screenshots and valid links)
BUT because Asus Flash Tool will wipe everything except user data and change your serial number from 0123456789ABCDEF to your legit serial number, flashing will NOT work and process will be ENDLESS because serial number has changed so phone is not found and you're not warned of that by Asus Flash Tool.
After 20 minutes of "OKAY" status displayed in green text on your phone, after 20 minutes of "a500cgfastboot.exe" running in task manager,
I think you can safely unplug USB cable, abort Asus Flash Tool by closing this software, killing "a500cgfastboot.exe",
rebooting phone (notice serial number change in fastboot info on phone's screen) and flash again with same settings but the new serial number (different of 0123456789ABCDEF).
This flash should work, after an hour or less you'll see in Asus Flash Tool that it's finished.
3. Flash Marshmallow zip with adb sideload
Finally, you'll have to shut down your phone,
boot in recovery mode (guide is here),
connect it to computer, select "apply update from adb",
install adb (link to ADB Installer 1.4.3 - Note: install it system-wide but don't install Android USB drivers) on your computer,
download zip OTA for Marshmallow (link to UL-Z008-WW-4.21.40.54-user.zip for ZE550ML / link to UL-Z00A-WW-4.21.40.61-user.zip for ZE551ML),
open a command prompt in the folder where you downloaded files (using "File > Open command prompt > Open command prompt" in the Windows Explorer's ribbon), then type :
Code:
adb devices
to verify that your phone is detected (you should see your serial number in cmd),
then type the following command to flash Marshmallow stock (zip is NOT pre-rooted if you want to root you'll have to do it after) :
ZE550ML
Code:
adb sideload UL-Z008-WW-4.21.40.54-user.zip
ZE551ML
Code:
adb sideload UL-Z00A-WW-4.21.40.61-user.zip
It may take a while decompressing then sending to phone. Then select "wipe cache partition" in your recovery menu,
wait until you see again the menu (so, wait until end of wiping cache), and select "reboot").
Now pray, and your device should magically boot the latest beautiful stock Marshmallow ROM from Asus, with all your data, exactly like before you bricked it.
It worked for me, but with the right new images it should work perfectly for you...
Enjoy this small guide, I hope you'll appreciate hard googling work
Thank you all, my problem is solved
fanfan54 said:
Solved without losing any data (except settings of some non-system apps)
Hello,
I found on ZenTalk (this thread : http://www.asus.com/zentalk/forum.php?mod=redirect&goto=findpost&ptid=78184&pid=392686) a working link to Latest Marshmallow sideload zip for ZE550ML OR ZE551ML. It was the right file, finally.
I sideloaded this file using adb and recovery mode, it worked PER-FECT-LY : my phone just rebooted without any problem, like before the problem. And with latest Marshmallow obviously : I immediately received messages, could access to my pictures, apps, with the same settings than before, in French (just one thing: settings for some non-system apps are reset)
Here is guide of everything I did to unbrick a Marshmallow ZE550ML stuck on USB logo with no bootloader :
(Note: I recommend you to charge your ZenFone for a few hours as soon as you'll get fastboot menu at step 1, so it will not shutdown... Even if it's not turning on the orange LED, it's charging )
(Note also that these are the steps I had to do in order to unbrick MY phone without losing data and installing Marshmallow. For your phone some steps might be unnecessary, if you're lucky... I know this is a very long guide but I had to do this in MY case)
1. Flash basic bootloader with xFSTK Downloader to boot fastboot
I had, first, to switch to advanced startup with support for unsigned drivers (video tutorial here),
install Asus USB drivers (link to Asus USB drivers here - note: video tutorial to install drivers from inf (repeat for every device available : ADB Interface, Bootloader Interface, etc...) )
and IntelSocUSB driver (link to IntelSocUSB driver 1.2.0 - Note: Before finishing IntelSocUSB setup it will ask you to configure a device : you'll have to connect your ZenFone 2 using an USB cable to your computer, while it's displaying USB logo, and WAIT FOR DETECTION IN Device Manager as "Moorefield device" under "Intel Soc" section),
to flash a fastboot bootloader (link to xFSTK_ZE550ML-sal358-amtech.vn for ZE550ML / link to xFSTK_ZE551ML-sal358-amtech.vn for ZE551ML) using xFSTK Downloader (link to xFSTK Downloader 1.7.0) [B
(guides for everything in this step 1: english version - same in vietnamese with screenshots and valid links - detailed PDF for xFSTK with screenshots).[/B] => phone boots on fastboot
2. Flash a lollipop ROM (or Marshmallow raw if you find it) with Asus Flash Tool to repair fastboot info (like serial number) and access recovery if you want to install Marshmallow from a zip
In order to get a working recovery menu (because I found a zip for Marshmallow but no raw, I'll have to install a recovery),
I had to install Asus Flash Tool (link to Asus Flash Tool 1.14 - Note: archive password is www.asus-zenfone.com ),
flash a Lollipop raw (link to WW_ZE550ML_2.20.40.149.raw) on my ZenFone 2 ZE550ML using Asus Flash Tool (Model: ZE550ML - wipe data : no)
(guides for everything in this step 2: english version - same in vietnamese with screenshots and valid links)
BUT because Asus Flash Tool will wipe everything except user data and change your serial number from 0123456789ABCDEF to your legit serial number, flashing will NOT work and process will be ENDLESS because serial number has changed so phone is not found and you're not warned of that by Asus Flash Tool.
After 20 minutes of "OKAY" status displayed in green text on your phone, after 20 minutes of "a500cgfastboot.exe" running in task manager,
I think you can safely unplug USB cable, abort Asus Flash Tool by closing this software, killing "a500cgfastboot.exe",
rebooting phone (notice serial number change in fastboot info on phone's screen) and flash again with same settings but the new serial number (different of 0123456789ABCDEF).
This flash should work, after an hour or less you'll see in Asus Flash Tool that it's finished.
3. Flash Marshmallow zip with adb sideload
Finally, you'll have to shut down your phone,
boot in recovery mode (guide is here),
connect it to computer, select "apply update from adb",
install adb (link to ADB Installer 1.4.3 - Note: install it system-wide but don't install Android USB drivers) on your computer,
download zip OTA for Marshmallow (link to UL-Z008-WW-4.21.40.54-user.zip for ZE550ML / link to UL-Z00A-WW-4.21.40.61-user.zip for ZE551ML),
open a command prompt in the folder where you downloaded files (using "File > Open command prompt > Open command prompt" in the Windows Explorer's ribbon), then type :
Code:
adb devices
to verify that your phone is detected (you should see your serial number in cmd),
then type the following command to flash Marshmallow stock (zip is NOT pre-rooted if you want to root you'll have to do it after) :
ZE550ML
Code:
adb sideload UL-Z008-WW-4.21.40.54-user.zip
ZE551ML
Code:
adb sideload UL-Z00A-WW-4.21.40.61-user.zip
It may take a while decompressing then sending to phone. Then select "wipe cache partition" in your recovery menu,
wait until you see again the menu (so, wait until end of wiping cache), and select "reboot").
Now pray, and your device should magically boot the latest beautiful stock Marshmallow ROM from Asus, with all your data, exactly like before you bricked it.
It worked for me, but with the right new images it should work perfectly for you...
Enjoy this small guide, I hope you'll appreciate hard googling work
Thank you all, my problem is solved
Click to expand...
Click to collapse
Man, Today you saved my life and my phone's life . I had exact same problem like yours and I have tried everything to bring my phone back to life last a few days. Today I just noticed your post and it solved my problem perfectly. Thanks man ,really appreciate it ..
muhammed cy said:
Man, Today you saved my life and my phone's life . I had exact same problem like yours and I have tried everything to bring my phone back to life last a few days. Today I just noticed your post and it solved my problem perfectly. Thanks man ,really appreciate it ..
Click to expand...
Click to collapse
Hello,
Thanks for your great feedback muhammed!
Have a nice day!
help me
fanfan54 said:
Hello,
Thanks for your great feedback muhammed!
Have a nice day!
Click to expand...
Click to collapse
please share to my email link WW_ZE550ML_2.20.40.149.raw
[email protected]
tanks before
iwakpauz said:
please share to my email link WW_ZE550ML_2.20.40.149.raw
[email protected]
tanks before
Click to expand...
Click to collapse
Hello, I already sent it to you by email. Here is the link : https://yadi.sk/d/XAUyR8eRtuKdA
Hello,
Sorry for reviving this thread, but I found myself in the same situation. I followed every step, and it works flawlessly. However, after flashing the stock Marshmallow ROM, unlocking the bootloader, flashing TWRP and reinstalling the stock ROM through there, it always bricks my phone (it's the ZE551ML, by the way), so I can't root my device at all. I wonder if anyone has any way of solving this?
I also found that, after unlocking the bootloader, the serial number appears as 0123456789ABCDEF again. I'm pretty much stuck on the stock ROM at this point, with no way of rooting it at all. I can't flash SuperSU through the stock recovery either, it gives me the "signature verification failed" error.
Thanks a lot in advance.
ayuinaba said:
Hello,
Sorry for reviving this thread, but I found myself in the same situation. I followed every step, and it works flawlessly. However, after flashing the stock Marshmallow ROM, unlocking the bootloader, flashing TWRP and reinstalling the stock ROM through there, it always bricks my phone (it's the ZE551ML, by the way), so I can't root my device at all. I wonder if anyone has any way of solving this?
I also found that, after unlocking the bootloader, the serial number appears as 0123456789ABCDEF again. I'm pretty much stuck on the stock ROM at this point, with no way of rooting it at all. I can't flash SuperSU through the stock recovery either, it gives me the "signature verification failed" error.
Thanks a lot in advance.
Click to expand...
Click to collapse
Hello , Firstly , although not clear when you say > "flashing TWRP and reinstalling the stock ROM through there"
1) You can only back up stock rom and restore from TWRP - you cannot flash stock rom from TWRP .
2) Were you bricked and used xFSTK at some point and did you correct serial before upgrading to M ?
signature failed is normal after unlocking bootloader :good:
timbernot said:
Hello , Firstly , although not clear when you say > "flashing TWRP and reinstalling the stock ROM through there"
1) You can only back up stock rom and restore from TWRP - you cannot flash stock rom from TWRP .
2) Were you bricked and used xFSTK at some point and did you correct serial before upgrading to M ?
signature failed is normal after unlocking bootloader :good:
Click to expand...
Click to collapse
Hello, and thank you for the reply!
I'm rather new to this, so I apologize for the possible incorrect terms... I'll try to describe everything as detailed as possible:
My device got bricked, and I sought a solution for it, thus arriving at this thread.
I did every step the OP described to unbrick the device, using xFSTK, *except* rebooting the device after the first flash with ASUS Flash Tool (because when I did, it'd become unresponsive, so I used the flash tool a second time without rebooting and it recovered my serial number).
Next, I went to recovery and installed the Lollipop .zip through adb sideload.
Afterwards, I installed the Marshmallow .zip through adb sideload again.
It's working great this way, but I wanted to root it, so I rebooted into bootloader, and tried to "fastboot boot twrp.img" with no success.
After reading a few more threads, I figured I had to unlock the bootloader before being able to boot into twrp, so I used the bootloader unlocker.
After unlocking it, I was unable to boot into anything but the bootloader (which I presume is normal), so I tried to boot into twrp through fastboot with no success - I had to use "fastboot flash recovery twrp.img" for it to work.
I went into recovery mode, and twrp launched. Since I presumed I had to install Marshmallow from there, due to unlocking the bootloader, I did - through "install .zip".
And after doing that and rebooting the system, it became unresponsive again, - bricked: black screen, only vibrates - thus returning to its initial state.
ayuinaba said:
Hello, and thank you for the reply!
I'm rather new to this, so I apologize for the possible incorrect terms... I'll try to describe everything as detailed as possible:
My device got bricked, and I sought a solution for it, thus arriving at this thread.
I did every step the OP described to unbrick the device, using xFSTK, *except* rebooting the device after the first flash with ASUS Flash Tool (because when I did, it'd become unresponsive, so I used the flash tool a second time without rebooting and it recovered my serial number).
Next, I went to recovery and installed the Lollipop .zip through adb sideload.
Afterwards, I installed the Marshmallow .zip through adb sideload again.
It's working great this way, but I wanted to root it, so I rebooted into bootloader, and tried to "fastboot boot twrp.img" with no success.
After reading a few more threads, I figured I had to unlock the bootloader before being able to boot into twrp, so I used the bootloader unlocker.
After unlocking it, I was unable to boot into anything but the bootloader (which I presume is normal), so I tried to boot into twrp through fastboot with no success - I had to use "fastboot flash recovery twrp.img" for it to work.
I went into recovery mode, and twrp launched. Since I presumed I had to install Marshmallow from there, due to unlocking the bootloader, I did - through "install .zip".
And after doing that and rebooting the system, it became unresponsive again, - bricked: black screen, only vibrates - thus returning to its initial state.
Click to expand...
Click to collapse
Hi again , yes you did everything right up to a point .
You will have to use xFSTK again , flash in aft after till you see ` RESULT = OK ` after a couple of minutes into flash (serial will be incorrect here) ...
Close aft - force close it - keep phone connected through-out -- do not dislodge data cable--- set everything back up in aft again -- then press vol+ once --- your serial will be corrected -- start the flash and let it finish , it will boot into the system related to the raw you flashed.
upgrade like before BUT when in M , use giovix`s Modder tool to unlock bootloader flash, twrp and root etc.
You will be fine ,just remember to back-up stock rom in TWRP first before installing custom LineageOS ,so you can use` return to stock option ` in modder tool after restoring your stock back-up -- to install future updates :good:
timbernot said:
Hi again , yes you did everything right up to a point .
You will have to use xFSTK again , flash in aft after till you see ` RESULT = OK ` after a couple of minutes into flash (serial will be incorrect here) ...
Close aft - force close it - keep phone connected through-out -- do not dislodge data cable--- set everything back up in aft again -- then press vol+ once --- your serial will be corrected -- start the flash and let it finish , it will boot into the system related to the raw you flashed.
upgrade like before BUT when in M , use giovix`s Modder tool to unlock bootloader flash, twrp and root etc.
You will be fine ,just remember to back-up stock rom in TWRP first before installing custom LineageOS ,so you can use` return to stock option ` in modder tool after restoring your stock back-up -- to install future updates :good:
Click to expand...
Click to collapse
Did everything as you told me, but now whenever I "reboot to system", it boots into recovery every time... :\
To clarify, I used the command "fastboot flash recovery twrp_z00a_v24_repack.img", and then installed the latest .zip of SuperSU in TWRP (Install -> SuperSU.zip).
EDIT: Sorry, I mistook Giovix's bootloader unlocker for their full modder tool, I'll be trying that now.
EDIT 2: You saved my butt! Thank you so much for your help, I managed to succeed in everything, finally!
ayuinaba said:
Did everything as you told me, but now whenever I "reboot to system", it boots into recovery every time... :\
To clarify, I used the command "fastboot flash recovery twrp_z00a_v24_repack.img", and then installed the latest .zip of SuperSU in TWRP (Install -> SuperSU.zip).
EDIT: Sorry, I mistook Giovix's bootloader unlocker for their full modder tool, I'll be trying that now.
EDIT 2: You saved my butt! Thank you so much for your help, I managed to succeed in everything, finally!
Click to expand...
Click to collapse
Marvelous stuff. ,its been a pleasure helping you
Happy flashing
---------- Post added at 02:47 AM ---------- Previous post was at 02:44 AM ----------
PS, should see the lengths some people go to restore serial
Why ? Lol When it
Only takes 3 mins max this way

[TuT]-How to unlock Samsung Smartphones FRP/FAP boot lock without "Loosing your data"

[TuT]-How to unlock Samsung Smartphones FRP/FAP boot lock without "Loosing your data"
How to reset FRP-Lock without Loosing your Data
HII..Guyss...
I am Nishant ...here to help you with your FRP-Locked Samsung Devices..
Now from hereby:- I am not Responsible if you gone Rabbit and done something wrong to your device
CAUSE:-
Actually this is beacuse you have flashed with custom binaries..
Custom binaries are like:-Custom Recovery(TWRP,CWM,SuperSU) or any other custom binaries that is not official.
Now these custom binaries modify boot sectors of your smartphone..
and these changes were not detected by your smartphone UNTIL and UNLESS you Turn off OEM-UNLOCK from DEVELOPER option..​Result:-​when you turn "OEM-UNLOCK to Off" OEM-LOCK will be enabled and on your next reboot (it also happens by mistake when you switch you developer option "switch")
OEM-Lock prevent your smartphone from booting with custom binaries...NOW,
.neither you can boot your phone nor you can access in Recovery-mode to wipe and reset..
and that prevent smartphone from booting with any custom binaries inside it..
So,
what now,if you know something about flashing than u have no choice offcourse either flash your smartphone with odin or you have to give it to
Samsung service center to make it work..which means loss of all your DATA (except extSdCard)
but,
I am here to solve your problem.. without Loosing a bit data of yours so, Follow me..
Solution:
1:-first download either your stock Firmware(I am not telling you to Flash your whole android smartphone).
Or...Manage to get your stock Boot.img and recovery.img file from anywhere on the web it is packed inside "your-Firmware.tar.md5" file
if you get your Boot and recovery.img file then skip to step 3
2:- Dwnloaded your firmware files now extract it using 7zip somewhere and copy out boot.img and recovery.img
3:- Download .img-to-tar from below and convert them from .img to .tar.md5 (odin-Flashable file)..
4:- Now first flash recovery.tar.md5 from odin to your smartphone.
5:-Secondly Flash boot.tar.md5 to your smartphone..
The Above Steps will reset your boot and recovery to stock version
Done......
Again its your Buddy Nishant...:good::good: ........enjoyy your FRP unlock
"Dont forget to turn on OEM-Unlock from developer option.."​
.
The title of your thread should be "How to fix Samsung Phones which get stuck on Samsung logo with "Custom binary blocked by FRP Lock" Cause your title means how to remove frp not how to solve the stuck problem ..
Thank you

Blackview BV9000 Pro-F ROOT SUCCESS [TWRP + Magisk v16 + Stock Rom]

EDIT: included rough procedures for OEM unlocking, and updated link to recovery-verified.img (Sorry for uploading the wrong file ><)
Hi all bv9000 pro Users!
Recently I went on a journey to root this awesome rugged phone with one purspose: to remove that F*@(#&$ god awful loud annoying sound triggered by the OS when you use a camera app to take a picture + the boot startup sound (A bug blackview hasn't gotten around to fixing).
I successfully managed to port TWRP 3.1.1 from the Blackview bv8000 Pro and run it on the Blackview bv9000 Pro-f!
I've then managed to flash in Magisk to gain root access.
DISCLAIMER: I do not take responsibility for any bricked phones caused by the process, do so at your own risk (yadayadayada).
NOTE 1: Although I've got it running on the bv9000 Pro-F, this image should also work for the non-fullHD version, if someone can test this I'd be happy.
The link to the stock ROM (with the modified recovery img) can be found in the post below.
NOTE 2: No need to download anything other than what I've listed, Magisk is included in my custom recovery to circumvent the need to load the devices encrypted storage (or any other external storage) nothing stops you from mounting external usb storage.
What you'll need:
- USB Mouse (As there is no touchscreen input support, your device should have come with a usb-c otg cable so there's no problem here!)
- MediaTek SP Flash tools (I'd recommend the latest version) https://spflashtool.com/
- unlocked bootloader (You should be able to do this via the developer settings -> unlock OEM Bootloader)
EDIT: To unlock the boot loader, do the following:
1) Go to settings -> unlock OEM Bootloader (tick)
2) plug your device in (assuming you have ADB installed), use adb to access fastboot via. command prompt:
"adb reboot bootloader"
Then once the device is rebooted into fastboot mode
"fastboot oem unlock"
KEEP IN MIND THIS WILL REMOVE ANY FILES, so back them up
- I've done this with windows, but you should be able to repeat with linux no problems!
- A little patience
Pre-preparation:
First install any updates and back up your data (it's just easiest to use the google cloud backup as restoring becomes easy as pie, updating also fixes the setup wizard crashing on first setup). This is necessary because OTA updates cannot be performed with TWRP recovery, and flashing TWRP before doing OTA updates will flick the device into a recovery boot loop.
Install the SP Flash tools, and the MediaTek VCOM Drivers
(I won't link the specifics here, a quick google search should be able to help you, just note you might need to disable driver signature enforcement)
Two options for flashing:
1)
My Full Stock ROM already pre-prepared for flashing:
Patched ROM
No need for extra prep here! you should just be able to load the scatter
2)
My custom patched TWRP stock rom: recovery-verified.img
Blackiew's stock rom: stock rom
- Download the stock rom, backup the recovery-verified.img in the R06 folder, and then replace it with my custom patched TWRP stock rom (file name should be the same).
- Run "CheckSum_Gen.exe" once you replaced the file, it will generate the necessary checksum to allow SP flash tools to successfully flash recovery.
Once you've done with the pre-prep, switch off your device, take a deep breath and you're ready to go!
Steps!
1) Load up SP Flash Tools, select the android scatter file you've downloaded in the R06 folder
2) Select Download Only (I MEAN IT, FORMATTING WILL REMOVE YOUR IMEI AND RENDER THE PHONE USELESS)
3) Deselect everything but recovery (You only want to flash this)
4) Hit download
https://pasteboard.co/HkufwZZ.png
5) Hold volume up + power and plug in your phone, keep the volume up button held
6) very quickly the flash should be complete, and you should be greeted with a big ol' green tick to verify
https://pasteboard.co/HkuiTBB.png
7) Once you're done, remove your USB cable, plug in the OTG then we proceed to flash magisk
8) Hold power + volume up until you reach the bootloader, then use the menu to select recovery
9) You *should* be greeted with the TWRP recovery screen (Which is great success! )
DON'T PANIC IF YOU CANNOT USE THE TOUCH SCREEN, the kernel I've patched is missing this, seems the driver is different between touch screens, just plug in your OTG mouse to continue from here!
10) Use your mouse to first hit cancel, we don't need to decrypt the user data storage.
11) But oh no! it's all in Russian (no problem, Next step sorts that)
12) Use your mouse to navigate the menus as shown here to change to English! (or your preferred language) Change Language
13) Click install, then navigate up folder levels until you are in the root directory
14) scroll down and click on Magisk.zip, install it, allow it to install any apps as system apps (because this will then install to the system image, not the userdata)
15) reboot the phone (if it hasn't rebooted already)
16) You should be able to boot into your usual phones OS, if you don't see Magisk listed in your phone apps, just download it from here:
Magisk Manager
17) Congratulations! You should have complete root access :laugh::laugh::laugh:
Feel free to express your thanks, or list any problems you have, but keep in mind my studies take all my life, so I may not be able to help with all the problems you have
Congrats! Would it work on the BV9000 HD version?
Hi!
From what I've seen they both run the helio p25 chip
(Just a difference in RAM size) so it should.
You're more than welcome to try.
Just keep a backup of the original ROMs recovery. If something goes wrong during the boot to recovery you can easily re flash
hi i tried both optinos but they didn't work for me
I tried the first and the second options and it was showed me same error:
ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
I tried download only, format all and download, if i install original ROM its installing without problems!
In settings-> developer options -> OEM unlocking is enabled
can someone give me tips if I'm doing something wrong. thanks
My phone is Blackview BV9000PRO-F
Hello,
i have the blackview 9000 pro Hd (not full hd)
i first tried your prepared patched rom = not working (get erorrers in step 6)
then i chose step 2 and i was thinking to use the stock rom from the NOT full hd rom
now i get a green screen from the flashing: but after rebooting in recovery nothing happens, just normal reboot then
perhaps this is not so clair for me:
- Download the stock rom, backup the recovery-verified.img in the R06 folder, and then replace it with my custom patched TWRP stock rom (file name should be the same).
- Run "CheckSum_Gen.exe" once you replaced the file, it will generate the necessary checksum to allow SP flash tools to successfully flash recovery.
the file name you posted here " My custom patched TWRP stock rom: recovery-verified.img" is ramdisk-recovery.img
i replaced the ramdisk-recovery.img... it is not clair need to replace recovery-verified.img to?
>I tried the first and the second options and it was >showed me same error:
>ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
> tried download only, format all and download, if i install >original ROM its installing without problems!
>can someone give me tips if I'm doing something wrong. >thanks
>My phone is Blackview BV9000PRO-F
Hi, you need to unlock the OEM bootloader, if this is still locked it will prevent the flashing of custom ROMS.
I might've missed this step, will update post as necessary.
>
dingsje said:
Hello,
>i have the blackview 9000 pro Hd (not full hd)
>i first tried your prepared patched rom = not working >(get erorrers in step 6)
>then i chose step 2 and i was thinking to use the stock >rom from the NOT full hd rom
>now i get a green screen from the flashing: but after >rebooting in recovery nothing happens, just normal >reboot then
>perhaps this is not so clair for me:
>- Download the stock rom, backup the recovery->verified.img in the R06 folder, and then replace it with >my custom patched TWRP stock rom (file name should >be the same).
>- Run "CheckSum_Gen.exe" once you replaced the file, >it will generate the necessary checksum to allow SP >flash tools to successfully flash recovery.
>the file name you posted here " My custom patched >TWRP stock rom: recovery-verified.img" is ramdisk->recovery.img
>i replaced the ramdisk-recovery.img... it is not clair >need to replace recovery-verified.img to?
Click to expand...
Click to collapse
Hi,
I've uploaded the wrong file, the uploaded file should be recovery-verified.img.
I'm uploading a new file and will correct the link now,
Please accept my apologies ><
hyperlethalvector92 said:
>I tried the first and the second options and it was >showed me same error:
>ERROR: STATUS INSUFFICIENT_BUFFER(0XC0010007)
> tried download only, format all and download, if i install >original ROM its installing without problems!
>can someone give me tips if I'm doing something wrong. >thanks
>My phone is Blackview BV9000PRO-F
Hi, you need to unlock the OEM bootloader, if this is still locked it will prevent the flashing of custom ROMS.
I might've missed this step, will update post as necessary.
Click to expand...
Click to collapse
I already did this step:
Enable developer options-> OEM unlocking is enabled
Is that enough for this MTK phone to be unlocked the bootloader ?
And tried the both options but the results are same.
I have been unlocking bootloaders on many phones but first time MTK phones. If i try with adb commands it recognize when is in the android with command adb devices and show my device but if I try reboot bootloader and check in device manager in windows its show its connected and drives are correct but if i try to show the devices, it doesn't show any device connected
Hi,
You need to install fastboot drivers once it's in bootloader mode,
then use fastboot, not adb.
"fastboot oem unlock"
Then follow instructions.
simply doing settings -> oem unlock won't unlock the bootloader, it allows you to do so later via. fastboot
Check the original post, I've added the extra instructions sorry about the confusion!
Thanks a lot. I finally succeeded to unlock the bootloader and root my phone and install the magisk.. I did without use your rom just I unlocked the bootloader and install your twrp file and after in the recovery mode i format the data and istall magic and i still have the last updated android.
I hope this it ill help to other people. Cheers
zlatkomas said:
Thanks a lot. I finally succeeded to unlock the bootloader and root my phone and install the magisk.. I did without use your rom just I unlocked the bootloader and install your twrp file and after in the recovery mode i format the data and istall magic and i still have the last updated android.
I hope this it ill help to other people. Cheers
Click to expand...
Click to collapse
I'm glad ^______^
Enjoy your rooted phone
I used this video to root my bv9000 pro hd
much easier than this above, i think it works to on bv9000 pro fhd
https://www.youtube.com/watch?v=c48ISLPjn4Q
Congratulations .... I need a tip,.
And, brother, thank you very much. Worked perfectly.
But first I would like to get you a tip ..
One of the main reasons I have done all this complicated process was to be able to disable the crap of the loud music that plays when the device is started.
I want complete silence at startup.
How do I disable this ****?
Code for Huawei mobile Wi-Fi e5577s-321
Pls help unlock my Huawei mobile Wi-Fi e5577s-321
Imei
860782038163889
TWRP looping after OTA update
My dear, the procedure worked very well, until an OTA update was downloaded.
You are now looping on TWRP. How do I get out of this?
:crying:
help!
i missed to run wireless software update,so ROM clashed.
How can i re-install custom ROM?
mackie_ma said:
help!
i missed to run wireless software update,so ROM clashed.
How can i re-install custom ROM?
Click to expand...
Click to collapse
Hi guys, lemme apologize for disappearing, life and whatnot!
For those stuck in a TWRP boot loop, simply restoring the original recovery then restarting the phone will be enough to fix the problem.
(Actually you really don't need TWRP after the phone is rooted, maybe I should update the guide?)
Many Thanks
First off, thank you for your hard work. Loved the "**** it we have an OTG cable let's use it" haha. It works fine for me.
Second, do you happen to know if someone has ported Oreo on our bv9000 ? Or do you know of any ETA ?
Thanks again,
Cheers
Anyone tried on the BV9000 Pro? Don't think mine is 'F' OR 'Fhd'.... I must have first model brought out...
Ugh.. Windows and Drivers?!?!
I keep getting Driver not Recognized in Windows 7 Pro X86.
I installed the latest vcom/usb drivers, in legacy also. No Go.
I installed from several other sources the drivers, including the Automatic Mediatek driver install. No Go.
So if anyone has a tip for me, please let me know because once more Windows is proving itself ridiculous. I can't even get to the storage of my phone. Did something change with a Windows Update that it's not allowed anymore?
I put my BV9000 Pro in OEM Unlock and USB Debugging. I backupped everything. My phone is ready for it. It's as ready as Amy having coitus with Sheldon for the first time.

Stuck at boot screen after trying to restart my device, don't want to lose data

Hey there, so I was playing a game PubG in which in the middle of a match the screen got stuck. I waited for 10 mins for it to go back and tried locking the screen with power button but nothing happened. When I long pressed it closed for a second then restarted and got stuck on bootscreen with only mi logo and no animation. Now it isn't switching off it gets rebooted to the same screen again. Only fastboot is opening. I don't want to lose my personal data there photos, videos that includes all my college life. If I try to flash it I think I will lose all data. Also I didnt backup all the data on mi cloud or anywhere. Please help me.
Also in flashing if I select the option 'save user data' will my data be saved?
same issue
same issue
happened to me just now
should be common software/update issue
Is your bootloader unlocked?
If you only want to back up your music, photos,videos,documents etc. , flash twrp recovery then boot into it (power+vol up about 11s). Connect your phone to PC. Then copy all data you need to save. Then reboot to fastboot and do a clean flash (clean all).
If you either want to back up the application data, do the previous operation without flashing first, and then do a "dirty" flash (save user data). At this time, your phone should be able to boot, use the BACKUP app to back up all your application data and copy it to your computer. The backup file seems to be stored in /storage/emulated/ 0/MIUI/backup, I don't remember it well.
After backing up all data you needed to save, you'd better do a clean flash using fastboot method. Make sure you choose "clean all".
Yuki1001 said:
Is your bootloader unlocked?
If you only want to back up your music, photos,videos,documents etc. , flash twrp recovery then boot into it (power+vol up about 11s). Connect your phone to PC. Then copy all data you need to save. Then reboot to fastboot and do a clean flash (clean all).
If you either want to back up the application data, do the previous operation without flashing first, and then do a "dirty" flash (save user data). At this time, your phone should be able to boot, use the BACKUP app to back up all your application data and copy it to your computer. The backup file seems to be stored in /storage/emulated/ 0/MIUI/backup, I don't remember it well.
After backing up all data you needed to save, you'd better do a clean flash using fastboot method. Make sure you choose "clean all".
Click to expand...
Click to collapse
Thanks for replyling. I think my bootloader is not unlocked. Also power+vol up is not working, only power+vol down is working. Can I flash twrp with bootloader locked?
Arun pm said:
same issue
happened to me just now
should be common software/update issue
Click to expand...
Click to collapse
So what did you do? Please tell me the method if you were able to solve it.
Re: Prakharpathak
I'm sorry because I can't save a phone that have a locked bootloader. If you wish to try Qualcomm QDLoader9008, maybe it will not work. Xiaomi has locked the 9008 port for their phones. Unless you have an authorized Mi account to get the verify token and send the authentitation tag to your phone, or the phone will reject all flashing commands. QPST is not working. The only difference is that the bootloader can be unlocked, but the 9008 requires authorization every time.
If you want to try the force unlock bootloader tool, once the force unlock is successful, you will lose all your data. Unless you can erase the recovery partition before the bootloader send a wipe command to Mi-recovery. In other words, if the recovery partition is erased or the recovery is not stock recovery (like twrp, etc) , unlocking the bootoader will not lose any data. Twrp does not accept the wipe command from the bootloader.
[edit]Now we have working firehose programmer could be used. Use QFIL to dump your userdata.
Yuki1001 said:
Re: Prakharpathak
I'm sorry because I can't save a phone that have a locked bootloader. If you wish to try Qualcomm QDLoader9008, maybe it will not work. Xiaomi has locked the 9008 port for their phones. Unless you have an authorized Mi account to get the verify token and send the authentitation tag to your phone, or the phone will reject all flashing commands. QPST is not working. The only difference is that the bootloader can be unlocked, but the 9008 requires authorization every time.
If you want to try the force unlock bootloader tool, once the force unlock is successful, you will lose all your data. Unless you can erase the recovery partition before the bootloader send a wipe command to Mi-recovery. In other words, if the recovery partition is erased or the recovery is not stock recovery (like twrp, etc) , unlocking the bootoader will not lose any data. Twrp does not accept the wipe command from the bootloader.
Click to expand...
Click to collapse
my bootloader is locked but i am ready to lose all my data , can you please tell me how can i boot my device
Re: @jagannath287
If this is also useful for you @Prakharpathak , you can also try.
If you are ready to lose all your data, you can try to use Mi PC Suite. Offical link of MI PC SUITE:
http://pcsuite.mi.com
You must be able to boot into Mi-Recovery, otherwise my solution will not help you.
Download the recovery ROM for your phone. Note that you can't upgrade or downgrade the OS version using this method.
After downloading and installing the Mi PC Assistant application on your computer, run it and login to your MI account. Then select FLASH ROM section and connect your device to your PC. Make sure your device is booted into Mi-recovery and selected “Connect with MiAssistant”.
Warning: you can't downgrade/change ROM region (you can only install the same area version to your phone, like MI-MI, RU-RU, EEA-EEA, etc) using this method.
Make a full wipe for your phone and select the RECOVERY ROM package: fast update and agree with full wipe. Then wait for the data erasing is fully done. After you see “Checking zip file update” and if all ok, the flashing progress will start and you will see the flashing is in progress. At last, you will see the window with successfully flashing. In theory, the phone will reboot to system automatically. The first start will take about 10 minutes. Be patient and wait the welcome screen.
There is another MI PC SUITE version that I found and I attach with my post. There is also a XiaomiADB flashing program.
Alternative method:
Download the adb driver and install it on your computer. Use the XiaomiADB full-auto flash program to flash your phone.
Select “Connect with MIAssistant” in the recovery and connect the phone to PC.
Make sure the recovery ROM zip file and XiaomiADB flashing program that in same folder. For start flashing just HOLD zip ROM AND DRUG IT TO THE XiaomiADB. After this command your DATA will be reset! You lost all files and Settings on your device.
At last, I suggest you to unlock the bootloader for your phone as soon as possible and flash your phone using MiFlash in fastboot mode in order to avoid facing mysterious bugs. A phone that have an unlocked bootloader is easy to save (unbrick) or backup all data from the phone without booting into system.
Attachment:
1.XiaomiADB:
https://drive.google.com/open?id=1BIlCd5wFFFlU2ObIQ-AtBNp3jlSj_5L1
2.MI PC SUITE 4.0 Beta:
https://drive.google.com/open?id=1_QoNlQFVj7lPo5iqM8jdrNmRwPztHQbV
If you find it useful, please click thanks.
I have an unlocked bootloader with latest stock rom
Stuck at MI logo
>No stock recovery loading
>Unfortunately the usb debugging is off (Automatically by MI security app :crying
>Tried Mi flash, Fastboot, Qualcomm Qflash with test point connection
>Is there anything left to try
Thanks
Re: @Arun pm
Xiaomi has locked the 9008 port for their devices.
Can you flash and boot into TWRP recovery?
Can your phone boots into fastboot?
Did you try to flash every partition manually?
Did you try to flash the oldest version--V9.5.19?
More information needed. It can save time and guesswork.
Yuki1001 said:
Re: @Arun pm
Thanks for the reply bro
Xiaomi has locked the 9008 port for their devices.
Can you flash and boot into TWRP recovery?
>> tried failed; stuck at the twrp logo(tried multiple versions and built)
Can your phone boots into fastboot? :
>>yes, but cant flash, permission error (usb debugging is off)
Did you try to flash every partition manually?
>>yes, even tried it with qualcomm tools but failed
Did you try to flash the oldest version--V9.5.19?
>>yes : same
More information needed. It can save time and guesswork.
Click to expand...
Click to collapse
Thanks for the reply bro
Xiaomi has locked the 9008 port for their devices.
Can you flash and boot into TWRP recovery?
>> tried failed; stuck at the twrp logo(tried multiple versions and built)
Can your phone boots into fastboot? :
>>yes, but cant flash, permission error (usb debugging is off)
Did you try to flash every partition manually?
>>yes, even tried it with qualcomm tools but failed
Did you try to flash the oldest version--V9.5.19?
>>yes : same
More information needed. It can save time and guesswork.
Re: @Arun pm
You'd better create a new thread otherwise we will disturb the original author of this thread (Prakharpathak).
Did you mean the returned message from your phone is like this:
Sending "recovery"...
OKAY. Total time: 4.016s
Writing "recovery"...
FAILED<remote: Permission Error>
finished. Total time: 4.016s
In theory, the fastboot won't return this message and the USB debugging switch has no relation with fastboot flashing.
All partitions can't be flashed and return the "permission error" message?
Can you take a photo of the flashing error message?
[edit] Now we have working programmer and you could do all you want via EDL.
Yuki1001 said:
Re: @Arun pm
You'd better create a new thread otherwise we will disturb the original author of this thread (Prakharpathak).
Did you mean the returned message from your phone is like this:
Sending "recovery"...
OKAY. Total time: 4.016s
Writing "recovery"...
FAILED<remote: Permission Error>
finished. Total time: 4.016s
In theory, the fastboot won't return this message and the USB debugging switch has no relation with fastboot flashing.
All partitions can't be flashed and return the "permission error" message?
Can you take a photo of the flashing error message?
Click to expand...
Click to collapse
I am currently facing a similar situation.
My device redmi note 5 pro was running on miui 11 and suddenly its screen froze and then it got restarted and stuck at mi logo. It has locked bootloader and I can't access the stock recovery but I can access fastboot mode. I tried flashing different miui versions with different flash tools and everytime the process starts then after 9 seconds I get the error "ack count doesn't match". I tried flashing with edl point method as well and with a patched firehose file to bypass mi authentication but still got the same error. Can you please help me? I searched around the net and I can't find anything related to this particular error I am getting. I would really appreciate if you can help.
oh god same issue its not booting, checked with service centre not able to update software, one of the mobile shop guy told that mobile mother board working fine but unable to locate software so that it can boot, now i am blank and helpless can you guys help me out please.. if people in chennai here let me know guys.. its been 5 th day without my mobile...
Hi,
I got similar issue. I had installed GFX tool for cod on redmi note 5 pro and got hang on call of duty mobile. After long press power button, got stuck at mi boot logo. Only able to do connect phone in fastboot to PC. Anybody found solution? I want to back up all data excluding apps. Kindly suggest working solutions.
Deep3004 said:
Hi,
I got similar issue. I had installed GFX tool for cod on redmi note 5 pro and got hang on call of duty mobile. After long press power button, got stuck at mi boot logo. Only able to do connect phone in fastboot to PC. Anybody found solution? I want to back up all data excluding apps. Kindly suggest working solutions.
Click to expand...
Click to collapse
Flash orangefox recovery, then boot to recovery and there you can disable all the apps you want
kadyt said:
Flash orangefox recovery, then boot to recovery and there you can disable all the apps you want
Click to expand...
Click to collapse
Thanks for reply.
I tried to flash orange fox recovery but bootloader is locked and no fastboot commands working. I have tried mi unlock flash tool to unlock bootloader but error is comming "couldn't unlock more devices by this account this month" on official tool and on unofficial tool error is "current account is not bounded to this device". I cannot add device to this account since phone is into bootloop and wanted to save data. Is there any way to unlock bootloader and get access to storage data?
Deep3004 said:
Thanks for reply.
I tried to flash orange fox recovery but bootloader is locked and no fastboot commands working. I have tried mi unlock flash tool to unlock bootloader but error is comming "couldn't unlock more devices by this account this month" on official tool and on unofficial tool error is "current account is not bounded to this device". I cannot add device to this account since phone is into bootloop and wanted to save data. Is there any way to unlock bootloader and get access to storage data?
Click to expand...
Click to collapse
Sorry I took for granted that you had the bootloader unlocked. Then I don't know. Hope someone else can help you
Anyway, if somehow you could unlock the bootloader now, as far as I know, you will lose your data when doing it
any development in the above event i am in the same stage

Question Unable to enter system after reboot

I am using 6 pro and got a huge problem.
My P6 pro is in fresh status and proceed a new setup with a new Google a/c. No matter in safe mode or normal mode, it always get into recovery mode - "can't load android system". Below picture is the log I capture from recovery mode. Could anybody help me? Thank you.
{
"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"
}
I know you said fresh setup, but just to be clear, did you attempt any sort of modification to your phone before this happened?
Can you try using this link to see if it'll help repair your device so it'll boot?
Google Pixel - Update and Software Repair
We need some more information.
What did you do with the device?
I can read Zygisk in the log. Do you have Magisk installed? What kind of modules do you have?
Have you flashed custom kernels/roms?
Can you access ADB/fastboot? You say you can access recovery mode, meaning you should be able to use
Android Flash Tool
flash.android.com
or
Google Pixel - Update and Software Repair
Did anything happen before you got this error message? (an action of yours ("I flashed this and that" or "the system updated?)? Or did this come "randomly"?
Hello friend, something similar happened to me when I wanted to unroot my pixel 6 pro. I got stuck in a bricked state and it told me that my device was corrupted.
If it is impossible to get into the device, but you can get into fastboot mode, I recommend you to follow this tutorial:
How to Unbrick Google Pixel 6/Pro via Fastboot Commands
In this tutorial, we will show you detailed steps to unbrick the Google Pixel 6 and Google Pixel 6 Pro via Fastboot Commands.
www.droidwin.com
EDIT: when you did the process of inserting the image, the device went into a mode called FASTBOOTD, you don't have to touch the device as the process is being done correctly.
Translated with www.DeepL.com/Translator (free version)
I think you need to provide a screenshot of the error message. Many of us had the "Device corrupt" message and its pretty easy to resolve. Try accessing Safe mode (as soon as you see the Google Logo, hold volume down) and enable "OEM Unlocking" - that way you can flash the factory image (not ota) and wipe the device, which will fix your phone.
edit--
Or before doing a reset, when in Safe mode, update Google Play Services, all apps, System Update and Play System (update all 4, I can help you with this if you need assistance -- this has resolved the corrupt error message for many users so try this before factory reset).
Morgrain said:
We need some more information.
What did you do with the device?
I can read Zygisk in the log. Do you have Magisk installed? What kind of modules do you have?
Have you flashed custom kernels/roms?
Can you access ADB/fastboot? You say you can access recovery mode, meaning you should be able to use
Android Flash Tool
flash.android.com
or
Google Pixel - Update and Software Repair
Did anything happen before you got this error message? (an action of yours ("I flashed this and that" or "the system updated?)? Or did this come "randomly"?
Click to expand...
Click to collapse
I did not root or install magdisk to the phone. I just openbox, turnon the phone, everything starts normal, do the setup and backup the data from my 4XL. Once completed, I recieve an update from sytem and requesting for reboot. Once I reboot the phone, goes into recovery and the screen said "cannot load android system. your data may be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device".
I have tried to flash the rom 12.0.0 (SQ1D.220105.007, Jan 2022) via developers : https://developers.google.com/android/images#raven
but no use and the phone still reboot into recovery mode after setup.
No matter I do the factory data reset or flash the rom again, it still goes into recovery mode after reboot
ecuchi said:
Hello friend, something similar happened to me when I wanted to unroot my pixel 6 pro. I got stuck in a bricked state and it told me that my device was corrupted.
If it is impossible to get into the device, but you can get into fastboot mode, I recommend you to follow this tutorial:
How to Unbrick Google Pixel 6/Pro via Fastboot Commands
In this tutorial, we will show you detailed steps to unbrick the Google Pixel 6 and Google Pixel 6 Pro via Fastboot Commands.
www.droidwin.com
EDIT: when you did the process of inserting the image, the device went into a mode called FASTBOOTD, you don't have to touch the device as the process is being done correctly.
Translated with www.DeepL.com/Translator (free version)
Click to expand...
Click to collapse
I did not root my device. Everything starts normal and i do the setup and backup the data from my 4XL. Once completed, I recieve an update from sytem and requesting for reboot. Once the phone reboots, it goes into recovery and the screen said "cannot load android system. your data may be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device".
I have tried to flash the rom 12.0.0 (SQ1D.220105.007, Jan 2022) via developers : https://developers.google.com/android/images#raven
but no use and the phone still reboot into recovery mode after setup.
No matter I do the factory data reset or flash the rom again, it still goes into recovery mode after reboot
Alekos said:
I think you need to provide a screenshot of the error message. Many of us had the "Device corrupt" message and its pretty easy to resolve. Try accessing Safe mode (as soon as you see the Google Logo, hold volume down) and enable "OEM Unlocking" - that way you can flash the factory image (not ota) and wipe the device, which will fix your phone.
edit--
Or before doing a reset, when in Safe mode, update Google Play Services, all apps, System Update and Play System (update all 4, I can help you with this if you need assistance -- this has resolved the corrupt error message for many users so try this before factory reset).
Click to expand...
Click to collapse
here is the screenshot. I try it in safemode to update all apps but still have the same problem. I also serval methods like setup the device as a new phone, boot into safe mode to update all apps, factory reset but the corrupt still remains after setup and reboot.
Here is the story : I got this phone on last friday, yesterday I openbox and turnon the phone and everything starts normal and do the setup and backup the data from my 4XL. Once completed, I recieve an update from sytem and requesting for reboot. Once I reboot the phone, goes into recovery and the screen said "cannot load android system. your data may be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device".
I have tried to flash the rom 12.0.0 (SQ1D.220105.007, Jan 2022) via developers : https://developers.google.com/android/images#raven
but no use and the phone still reboot into recovery mode after setup.
No matter I do the factory data reset or flash the rom again, it still goes into recovery mode after reboot
RetroTech07 said:
I know you said fresh setup, but just to be clear, did you attempt any sort of modification to your phone before this happened?
Can you try using this link to see if it'll help repair your device so it'll boot?
Google Pixel - Update and Software Repair
Click to expand...
Click to collapse
No, I did not do any modification. I also try the pixel repair but no use.
jozifkwan said:
here is the screenshot. I try it in safemode to update all apps but still have the same problem. I also serval methods like setup the device as a new phone, boot into safe mode to update all apps, factory reset but the corrupt still remains after setup and reboot.
Here is the story : I got this phone on last friday, yesterday I openbox and turnon the phone and everything starts normal and do the setup and backup the data from my 4XL. Once completed, I recieve an update from sytem and requesting for reboot. Once I reboot the phone, goes into recovery and the screen said "cannot load android system. your data may be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device".
I have tried to flash the rom 12.0.0 (SQ1D.220105.007, Jan 2022) via developers : https://developers.google.com/android/images#raven
but no use and the phone still reboot into recovery mode after setup.
No matter I do the factory data reset or flash the rom again, it still goes into recovery mode after reboot
Click to expand...
Click to collapse
I have seen this Scenario hours ago when I try to disable vbmeta to get the corrupted message appearing after booting.
Because I disabled vbmeta flags, wiping is necessary, therefore I choose factory data reset. issue fixed, data lost. that's all
jozifkwan said:
here is the screenshot. I try it in safemode to update all apps but still have the same problem. I also serval methods like setup the device as a new phone, boot into safe mode to update all apps, factory reset but the corrupt still remains after setup and reboot.
Here is the story : I got this phone on last friday, yesterday I openbox and turnon the phone and everything starts normal and do the setup and backup the data from my 4XL. Once completed, I recieve an update from sytem and requesting for reboot. Once I reboot the phone, goes into recovery and the screen said "cannot load android system. your data may be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device".
I have tried to flash the rom 12.0.0 (SQ1D.220105.007, Jan 2022) via developers : https://developers.google.com/android/images#raven
but no use and the phone still reboot into recovery mode after setup.
No matter I do the factory data reset or flash the rom again, it still goes into recovery mode after reboot
Click to expand...
Click to collapse
okay, this is what you do:
Boot into Safe mode (either boot into Android and hold restart option or turn phone off, hold power button until you see Google Logo, when you see it, let go of power and hold Volume Down button)
Now disable Bluetooth and enable Wifi (it will be disabled so make sure you do this). Then force stop Play Store app. Long-press on shortcut, my apps, update all. Make sure you do these steps exactly as written.
Then open this link in Google Chrome (must be opened in your default browser so it opens the hidden Play Services app in Google Play Store), it will open Google Play Services. hit update, it takes 45 seconds to install in the background.
While that is updating, go to Android Settings, Security and update both System Security and Play System. Now restart your phone.
I've helped approximately 8 or 9 users on reddit in December and January with this method so hopefully that works.
I also had this issue in December after updating the December Update. The only way I could fix it was by using the Android Flash Tool and installing the November Factory Image (not OTA) and picking wipe phone and flash all partitions. read on...
Try the Official Android Flash Tool (link below), on that page hit the "pencil" and you will see advanced options - check the boxes for "Wipe Device" and "Flash All Partitions" (no need to relock the bootloader just yet until you fix your phone).
If you are using windows, download the latest Google USB driver file from the link below), extract the file and right-click on the Android_winusb.inf file and hit "install". Now when you are using the Official Flash Tool website or command line, make sure you are in the Bootloader Menu (Fastboot Screen) where it says "Device State: Locked/Unlocked" and you have the options to boot into recovery/rescue mode etc. That's the Bootloader (looks like you've flashed the image already but maybe it didn't work so using the Android Flash tool is recommended). For the Flash Tool, you'll need to use Google Chrome and also disable adblockers and don't use incognito mode during the process.
USB Drivers for Google Devices:
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Android Flash Tool:
Android Flash Tool
flash.android.com
You can also go to the Android Factory Image Download Page, and try a different Build from October or November. Do that by clicking the blue "Flash" word (not the link to downlod) beside the Build Number which will also take you to the Android Flash Tool website (the Android Flash Tool has two different pages which do the same thing, back-to-public and the direct "Flash" page for a specific build). For example, under the Pixel 6 Pro, for November, there's a build Number 12.0.0 (SP1A.211105.003, Nov 2021) and beside that you can flash the image using the Android Flash Tool or download the full image like you've previously done.
Alekos said:
okay, this is what you do:
Boot into Safe mode (either boot into Android and hold restart option or turn phone off, hold power button until you see Google Logo, when you see it, let go of power and hold Volume Down button)
Now disable Bluetooth and enable Wifi (it will be disabled so make sure you do this). Then force stop Play Store app. Long-press on shortcut, my apps, update all. Make sure you do these steps exactly as written.
Then open this link in Google Chrome (must be opened in your default browser so it opens the hidden Play Services app in Google Play Store), it will open Google Play Services. hit update, it takes 45 seconds to install in the background.
While that is updating, go to Android Settings, Security and update both System Security and Play System. Now restart your phone.
I've helped approximately 8 or 9 users on reddit in December and January with this method so hopefully that works.
I also had this issue in December after updating the December Update. The only way I could fix it was by using the Android Flash Tool and installing the November Factory Image (not OTA) and picking wipe phone and flash all partitions. read on...
Try the Official Android Flash Tool (link below), on that page hit the "pencil" and you will see advanced options - check the boxes for "Wipe Device" and "Flash All Partitions" (no need to relock the bootloader just yet until you fix your phone).
If you are using windows, download the latest Google USB driver file from the link below), extract the file and right-click on the Android_winusb.inf file and hit "install". Now when you are using the Official Flash Tool website or command line, make sure you are in the Bootloader Menu (Fastboot Screen) where it says "Device State: Locked/Unlocked" and you have the options to boot into recovery/rescue mode etc. That's the Bootloader (looks like you've flashed the image already but maybe it didn't work so using the Android Flash tool is recommended). For the Flash Tool, you'll need to use Google Chrome and also disable adblockers and don't use incognito mode during the process.
USB Drivers for Google Devices:
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Android Flash Tool:
Android Flash Tool
flash.android.com
You can also go to the Android Factory Image Download Page, and try a different Build from October or November. Do that by clicking the blue "Flash" word (not the link to downlod) beside the Build Number which will also take you to the Android Flash Tool website (the Android Flash Tool has two different pages which do the same thing, back-to-public and the direct "Flash" page for a specific build). For example, under the Pixel 6 Pro, for November, there's a build Number 12.0.0 (SP1A.211105.003, Nov 2021) and beside that you can flash the image using the Android Flash Tool or download the full image like you've previously done.
Click to expand...
Click to collapse
I try your method but problems still same. After flash the factory rom(SD1A.210817.036), the phone always goes to welcome screen setting(fresh status). I have tried to boot in safe mode, turn off bluetooth and do your step but problem still the same. As long as the phone reboot , it goes to recovery mode and said "cannot load android system. your data may be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device".
I feel like the phone can not save data on userdata(metadata?) or the userdata(metadata?) file system corrupt? do I need to format the userdata(metadata?) to ext4 to make it stable?
jozifkwan said:
I try your method but problems still same. After flash the factory rom(SD1A.210817.036), the phone always goes to welcome screen setting(fresh status). I have tried to boot in safe mode, turn off bluetooth and do your step but problem still the same. As long as the phone reboot , it goes to recovery mode and said "cannot load android system. your data may be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device".
I feel like the phone can not save data on userdata(metadata?) or the userdata(metadata?) file system corrupt? do I need to format the userdata(metadata?) to ext4 to make it stable?
Click to expand...
Click to collapse
Ok, can you try this:
Go to recovery Mode, wipe/factory reset. When its done, hit "restart bootloader" then go here and flash this:
Android Flash Tool
flash.android.com
Let it complete, the phone will restart 2 or 3 times by itself. You will see a "Fastbootd" screen (yes with a 'd') and it will show a few options, don't touch the phone, let the Flash tool do its thing. You will see a bunch if information on the website such as "flashing... writing... etc etc" - let it finish and it will restart by itself.
On that website, pick "wipe phone" and "flash all partitions" - this is important, keep every other option unchecked.
Can you try that and make sure it completes 100%?
Also, I would try flashing each boot slot separately . So use the above flash tool to flash the first slot (for example a) then switch slots and flash again.
the commands to change boot slots is here:
fastboot --set-active=a (to change from b to a)
fastboot --set-active=b ( to change from a to b)
the bootloader (fastboot menu) will show at the bottom what Boot slot is being used.
Alekos said:
Ok, can you try this:
Go to recovery Mode, wipe/factory reset. When its done, hit "restart bootloader" then go here and flash this:
Android Flash Tool
flash.android.com
Let it complete, the phone will restart 2 or 3 times by itself. You will see a "Fastbootd" screen (yes with a 'd') and it will show a few options, don't touch the phone, let the Flash tool do its thing. You will see a bunch if information on the website such as "flashing... writing... etc etc" - let it finish and it will restart by itself.
On that website, pick "wipe phone" and "flash all partitions" - this is important, keep every other option unchecked.
Can you try that and make sure it completes 100%?
Also, I would try flashing each boot slot separately . So use the above flash tool to flash the first slot (for example a) then switch slots and flash again.
the commands to change boot slots is here:
fastboot --set-active=a (to change from b to a)
fastboot --set-active=b ( to change from a to b)
the bootloader (fastboot menu) will show at the bottom what Boot slot is being used.
Click to expand...
Click to collapse
Thank you, I tried your guideline to flash, tick "wipe" and "flash all partitions", flash slot A first and then flash slot B.
The problem is still the same, once I finished the setup, reboot, goes into recovery again and said "cannot load android system"
Beginning to sound like you should exchange it for a new one, unfortunately.
Got me a bit paranoid all these devices not able to boot anymore due to corrupted data. Mine says corrupted when going to boot phone, have to press power to continue then warning of attackers then boots fine hoping this corrupt message and the amount of times one reboots without correcting the error is not the reason for bricked devices
Sounds like a hardware issue with the NAND.
LLStarks said:
Sounds like a hardware issue with the NAND.
Click to expand...
Click to collapse
I believe it is not the NAMD.
Last night, I test the battery to see if the corruption issue is caused by unstable voltage or ampere. I run drain app + 3D mark, my phone of course heats up but no reboot or unstable issue.
The battery test drained 60% of battery and i manually reboot the phone, no problems or errors and enter system. Then I left the phone in stanby mode for 7 hours. The battery downs to 35% and I reboot the phone again but this time unfortunately goes into recovery issue again.
This is very weired and I couldn't figure out what kind of problem is that.
stevendeb25 said:
Got me a bit paranoid all these devices not able to boot anymore due to corrupted data. Mine says corrupted when going to boot phone, have to press power to continue then warning of attackers then boots fine hoping this corrupt message and the amount of times one reboots without correcting the error is not the reason for bricked devices
Click to expand...
Click to collapse
I am wondering if anyway to skip the recovery or corrupt checking.
stevendeb25 said:
Got me a bit paranoid all these devices not able to boot anymore due to corrupted data. Mine says corrupted when going to boot phone, have to press power to continue then warning of attackers then boots fine hoping this corrupt message and the amount of times one reboots without correcting the error is not the reason for bricked devices
Click to expand...
Click to collapse
you have the corrupt message also? Can you try what I recommended above, updating all 4 Play Services/Play Store Apps/Security Update and Play System Update with Bluetooth disabled?
If not use the Android Flash Tool and wipe the device and flash all slots, let us know if that works.

Categories

Resources