Hello community!
Ive tryed to flash my phone from firmware 366 to 369 so i've used this script to flash thouse files:
fastboot -i 0x413c flash amss amss.mbn
fastboot -i 0x413c flash dsp1 dsp1.mbn
fastboot -i 0x413c flash fsb fsbl.mbn
fastboot -i 0x413c flash osbl osbl.mbn
fastboot -i 0x413c flash appsboot appsboot.mbn
fastboot -i 0x413c flash dbl dbl.mbn
fastboot -i 0x413c flash DT DT.img
fastboot -i 0x413c flash boot boot.img
fastboot -i 0x413c flash recovery recovery.img
after rebooting my phone doesn''t tourn on anymore! I've tryed to "reanimate" device with StreakFlash buy phone doesnt want to install the driver while pressing Vol-UP Button.
Help me please!
Of course it won't. If I'm not mistaken the 366 and 369 ROMs are Softbank ROMs? The last couple ROM updates from them I believe were not in the form of patches but full-blown ROM updates like the rest of the world, and thus you shouldn't have needed to manually flash through Fastboot all those files.
The QDL Tool may revive the Streak, but be prepared to have the device JTAGged, and thus lose phone capability as a result.
EDIT: Did your script execute a fastboot -w or fastboot -erase command at the end?
Strephon Alkhalikoi said:
Of course it won't. If I'm not mistaken the 366 and 369 ROMs are Softbank ROMs? The last couple ROM updates from them I believe were not in the form of patches but full-blown ROM updates like the rest of the world, and thus you shouldn't have needed to manually flash through Fastboot all those files.
The QDL Tool may revive the Streak, but be prepared to have the device JTAGged, and thus lose phone capability as a result.
EDIT: Did your script execute a fastboot -w or fastboot -erase command at the end?
Click to expand...
Click to collapse
no this is the exact sript ive used to flash the files
QDL Tool doesnt work ive tryed already
Rocker19943 said:
no this is the exact sript ive used to flash the files
QDL Tool doesnt work ive tryed already
Click to expand...
Click to collapse
I'm sorry for you, cause your device is dead. Who told you to run these commands?
Anyway. There are three solutions I can think off:
(1) Have your device JTAGed. If you are very lucky and do not overwrite SIM_SECURE and RESERVED partitions your Streak will work again. But I don't think you will have such luck. Besides you need a technican that opens your device without breaking it and have the right tools to JTAG it. They are expensive. Even if you killed SIM_SECURE-partition you may recover one with revskills.de or simsecure.dll with QC BQS Firmware Analyzer.
(2) Buy a broken screen device on ebay and change the pcb with your device. You also need luck, to get an honest seller and a technican.
(3) Cut your losses and sell your device for parts (screen and camera are most asked for)
Good luck,
hunderteins
hunderteins said:
I'm sorry for you, cause your device is dead. Who told you to run these commands?
Anyway. There are three solutions I can think off:
(1) Have your device JTAGed. If you are very lucky and do not overwrite SIM_SECURE and RESERVED partitions your Streak will work again. But I don't think you will have such luck. Besides you need a technican that opens your device without breaking it and have the right tools to JTAG it. They are expensive. Even if you killed SIM_SECURE-partition you may recover one with revskills.de or simsecure.dll with QC BQS Firmware Analyzer.
(2) Buy a broken screen device on ebay and change the pcb with your device. You also need luck, to get an honest seller and a technican.
(3) Cut your losses and sell your device for parts (screen and camera are most asked for)
Good luck,
hunderteins
Click to expand...
Click to collapse
thought so that its dead. Thanks! now im more sure thats its not possible to repair, gonna buy new one
The question still remains: who told you to run all these commands?
Strephon Alkhalikoi said:
The question still remains: who told you to run all these commands?
Click to expand...
Click to collapse
Noone, I was thinking that all of thouse files were made for the correct rom, so i thought that there will not be any problem after flashing
Rocker19943 said:
Noone, I was thinking that all of thouse files were made for the correct rom, so i thought that there will not be any problem after flashing
Click to expand...
Click to collapse
But who told you to flash them like that is what we're dying to know. Why not flash the update.pkg via Dell recovery?
Sent from my Dell Streak using Tapatalk 2
cdzo72 said:
But who told you to flash them like that is what we're dying to know. Why not flash the update.pkg via Dell recovery?
Sent from my Dell Streak using Tapatalk 2
Click to expand...
Click to collapse
everybody learn on their own mistake anyway ive already tired of that phone
Rocker19943 said:
Hello community!
Ive tryed to flash my phone from firmware 366 to 369 so i've used this script to flash thouse files:
fastboot -i 0x413c flash amss amss.mbn
fastboot -i 0x413c flash dsp1 dsp1.mbn
fastboot -i 0x413c flash fsb fsbl.mbn
fastboot -i 0x413c flash osbl osbl.mbn
fastboot -i 0x413c flash appsboot appsboot.mbn
fastboot -i 0x413c flash dbl dbl.mbn
fastboot -i 0x413c flash DT DT.img
fastboot -i 0x413c flash boot boot.img
fastboot -i 0x413c flash recovery recovery.img
after rebootinh my phone doesnt tourns on anymore! I've tryed to "reanimate" device with StreakFlash buy phone doesnt want to install the driver while pressing Vol-UP Button.
Help me please!
Click to expand...
Click to collapse
Dear friend Rocker19943, my phone was same one year ago. Only way to repair with complete instructions is HERE. After, is possible that you need download files .pkg for 351 version (actually I have this version in my Streak 5 and work fine!!!!) for HERE.
My mail is [email protected]
Friend, YOU NEVER GIVE IN!!!!!!
Good luck....
@wear90: Remove your email address unless you want to be flooded with spam.
ok lets see, after JTAGing my device its now tourns on, so i have used QDLtool
Here is the log, everything was success!
Code:
HW:
Board ID:
Comment:
--
LOG
--
###QDLTool: M 2.7.4.5, build ID: 1.302.20100910, time stamp: Sun Dec 30 17:27:39 2012
Check image DBL: C:\Users\Rocker\Desktop\streakflash\images\dbl.mbn ...
Check image FSBL: C:\Users\Rocker\Desktop\streakflash\images\fsbl.mbn ...
Check image OSBL: C:\Users\Rocker\Desktop\streakflash\images\osbl.mbn ...
Check image AMSS: C:\Users\Rocker\Desktop\streakflash\images\amss.mbn ...
Check image DSP1: C:\Users\Rocker\Desktop\streakflash\images\dsp1.mbn ...
Check image APPSBL: C:\Users\Rocker\Desktop\streakflash\images\appsboot.mbn ...
Check image DT: C:\Users\Rocker\Desktop\streakflash\images\DT.img ...
Check images: Partition Dbl Fsbl Osbl Amss Dsp1 DT Appsbl
Check images ok
Download in speedup way
Open COM port success
OSBL version: 12-5035-AUSB1AM-09
osbl.mbn version:
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Open COM port success
Test communication success
Check Secure Boot is enabled
#DBL to DDR success
#FSBL to DDR success
#OSBL to DDR success
#AMSS to DDR success
#DSP1 to DDR success
#DT to DDR success
#APPSBL to DDR success
#backup FSBL to DDR success
#backup OSBL to DDR success
#backup DT to DDR success
#backup APPSBL to DDR success
Run HEX success
Check Secure Boot is enabled
Streaming hello success
Send Security mode success
Download partition table success
#Download DBL success
#Download FSBL success
#Download OSBL success
#Download AMSS success
#Download DSP1 success
#Download DT success
#Download APPSBL success
#Download backup FSBL success
#Download backup OSBL success
#Download backup DT success
#Download backup APPSBL success
Erase EFS2 success
Wait for rebooting ....... ok
Wait for modem set up ......
Download success - 2012/12/30 17:29:02
Elapsed Time: 82.11 sec
BUT, when device is trying to load the system its getting into recovery and giving the following error
E: Can't mount /dev/block/mmcblk1 ( or /dev/block/mmcblk0)
------
EDIT: System has been installed but the device stuck at Dell logo
Also before getting into fastboot menu it shows in a red line (Default NV checked #3)
EDIT 2: Dont care for errors!!! NOW IT WORKS!!!!
Here what have i done
1: Formated internal MicroSD with linux Gparted tool [WARNING ITS DANGEROUS!!! - Better not to do]
2: Used Streakflash (QDL) Tool to start the device
3: Went to fastboot and flashed 360's amss.mbn and ds1.mbn
4: Flashed modificated recovery
5: After reboot Ive opened Recovery menu, wiped cache partition, dalvik cash, Battery stats and everything which could be wiped ;D
6: Installed DSC 2.0 ROM
7: After rebooting I have done factroy reset from Dell menu and then, after 5 minutes my phone started up
EDIT3: SIM Doesnt work even if it can pass test in dev menu
I read in net that because of JTAG Phone has got locked! Well even the Unlock code wont help, I have kinda lost cell functuions :L sad
Guys, on forums i read that after JTAGing Service Tag of device should be 0000000
but in my device its not zeros, so is there a way to unlock it again?
Rocker19943 said:
EDIT3: SIM Doesnt work even if it can pass test in dev menu
I read in net that because of JTAG Phone has got locked! Well even the Unlock code wont help, I have kinda lost cell functuions :L sad
Click to expand...
Click to collapse
if you read carefully on this forum... jtagging your phone would make the phone capabilities goes down the drain... the only way to add the phone function back is by using the external bluetooth hardware...
i have posted in the general forum ... but seems nobody has ever use it so no feedback at all...
The question still follows
The service tag has nothing to do with the loss of phone capability. In the case of the loss of phone capability, JTAGging the Streak basically wipes out the low-level firmware that interfaces with the SIM card. There's no way to restore the firmware and no way of using the phone parts of a Streak that has been JTAGged, short of replacing the Streak's motherboard.
Rocker19943 said:
...
Erase EFS2 success
Wait for rebooting ....... ok.
EDIT3: SIM Doesnt work even if it can pass test in dev menu
I read in net that because of JTAG Phone has got locked! Well even the Unlock code wont help, I have kinda lost cell functuions :L sad
Click to expand...
Click to collapse
Way old thread. But FWIW, you erased EFS2 which contain SIM critical data etc. You need to use replace this...
Related
im trying to unlock bootloader and i have downloaded the pudding sbf file (derpunlock.sbf)
but with no succes it failed everytime im trying to flash
flash error log :
00:41:34, October 07, 2011
Line: 768
ERROR: Phone[0001]: The "Secure_Motorola_Flash" Interface could not be found.
The super-file is secure and for re-flash;
the phone needs a super-file that is not secure and not for re-flash.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\MIFlash.cpp
Device ID: 1
00:41:34, October 07, 2011
Line: 610
ERROR: Flash failure: Phone[0001]: The "Secure_Motorola_Flash" Interface could not be found.
The super-file is secure and for re-flash;
the phone needs a super-file that is not secure and not for re-flash. (Error Code: 66),
Detailed Error Details: Direction of the Error=No Direction, Command Value=0, Code Group Number=255
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 1
please help , thanks
salim said:
im trying to unlock bootloader and i have downloaded the pudding sbf file (derpunlock.sbf)
but with no succes it failed everytime im trying to flash
flash error log :
00:41:34, October 07, 2011
Line: 768
ERROR: Phone[0001]: The "Secure_Motorola_Flash" Interface could not be found.
The super-file is secure and for re-flash;
the phone needs a super-file that is not secure and not for re-flash.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\MIFlash.cpp
Device ID: 1
00:41:34, October 07, 2011
Line: 610
ERROR: Flash failure: Phone[0001]: The "Secure_Motorola_Flash" Interface could not be found.
The super-file is secure and for re-flash;
the phone needs a super-file that is not secure and not for re-flash. (Error Code: 66),
Detailed Error Details: Direction of the Error=No Direction, Command Value=0, Code Group Number=255
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 1
please help , thanks
Click to expand...
Click to collapse
1) Take a deep breath - everything is okay
2) You're supposed to get that error
3) Pull the battery after your phone freezes up
4) Get into fastboot mode (power + Vol down)
5) Run the Moto-fastboot command to confirm being unlocked
You're set!
thanke u for helping ,
i just run the cmd command moto-fastboot and it has show me a list of options and commands... thats what it should happens ?
and when i reboot in fastboot it havent shown me that it unlocked... ( i just got my photon yesterday.. )
salim said:
thanke u for helping ,
i just run the cmd command moto-fastboot and it has show me a list of options and commands... thats what it should happens ?
and when i reboot in fastboot it havent shown me that it unlocked... ( i just got my photon yesterday.. )
Click to expand...
Click to collapse
Hmm...when you flash the unlocker, it will fail. This has exactly happened to me. I then proceeded to pull the battery. When I power on the phone again, it should say "Unlocked" at the top above the motorola screen. When you put into fastboot mode, press volume up and start the moto-fastboot commands:
- Type moto-fastboot oem unlock
- Look for the UNIQUE ID number and copy it, use copy or your fat fingers might mistype it.
- Type moto-fastboot oem unlock YOUR_UNIQUE_ID_THAT_YOU_JUST_COPIED
(from the original thread)
It should say "Your phone is already unlocked" or something like that....
- type moto-fastboot reboot or fastboot reboot depending
You should be all set...I'm not sure why it wouldn't say "Unlocked" when powering on the phone again...Try again...just make sure to fully charge your phone, plug it into the back of the computer, and wait for the unlocker to fail. It shouldn't take that long...keep trying!
thanke u very much ! you realy helped me =]
salim said:
thanke u very much ! you realy helped me =]
Click to expand...
Click to collapse
No problem..just hit that "Thanks" button..I'd appreciate it!
Hey Guys,
I tried flashing my rom to CM7 and in the process the phone rebooted and got the error message
SVF:105:1:2
failed to boot 0x1000
No OS detected, going to RSD mode
in 5 seconds
Press a key to stop countdown
Available modes are:
1. RSD
2. Fastboot
3. NVFlash
4. BP HW Bypass RSD
5. BP HW Bypass QC Dload
6. BP Diag & boot AP
7. BP HW bypass BP only
8. BP SW bypass RSD
9. Andriod Recovery
10 .Boot andriod (No BP)
11. Device UID
12. console=ttyS0,115200n8
13. Early USB Enumeration
14..BP tools
I get the error message in the rsd lite as error switching to BP and something.
Kindly help i am really confused.
Soft brick .
Download moto-fastboot, and unzip to C:\moto-fastboot
DL here:http://www.android-advice.com/file-d...rix_Root_Files
Download system image for 2.3.4 and unzip to moto-fastboot folder
DL here http://www.android-advice.com/file-d...bread_4591_ROM
Download atrix oem unlock and unzip to moto-fastboot folder
DL here:http://gititbit.ch/pub/unlock.zip
open cmd and navigate to C:\moto-fastboot\
Force fastboot on phone by holding down PWR and VOL UP while inserting battery.
Type these commands:
moto-fastboot oem unlock (it will show atrix ID re-enter with ID at end of line)
when finished, then enter these commands:
moto-fastboot flash boot boot.img
moto-fastboot flash system system.img
moto-fastboot -w
moto-fastboot reboot
When it reboots, you will be back to stock, fully restored!!
I then used Pete's Motorola Tools to root my atrix.
Info and DL here http://www.psouza4.com/Bionic/
yes it did work on my atrix make sure usb debugging is on and unknown sources checked.
I then installed CWM to my Atrix
DL here http://forum.xda-developers.com/show....php?t=1475444
unzip to moto-fastboot, put atrix in fastboot mode and open cmd, navigate to moto-fastboot folder and type this:
moto-fastboot flash recovery recovery.img
Reboot and you are DONE!!!! All thats left is to find a ROM and you are good to go
No need to do all that.
Since you want to get CM7, Unlock the phone.
Ignore the instructions to flash system.img, that will bring you back to stock.
Enter fastboot, flash a recovery. (Above post last instruction)
Enter recovery mode, than flash CM7 from there.
(I assume you are familiar with what I am talking about, and don't require step by step instructions)
Bricked
Thank u for ur replies i havent tried it yet but i wish it wud work i was using the latest update from AT&T i think since i tried to boot for the older version this happened i am not sure though.
There has been posts about trying to unlock after applying AT&T latest update. You should read up on those, I remember it could brick your phone, be careful!
Thank You
Dear All,
Thank u a hundred thousand times for helping me get rid of the problem i owe u guys a lot finally got to work.
Thank u once again i dont have words to describe my joy.At ant time u want help in India count me in.
this happened to me to, all i did was go to fastboot and unlock the bootloader and it let me boot again after recovering to a rom i had on my SD. i did try and install a custom recovery when it bricked.
HI ranjit
Hi ranjith
need your help
can u drop in ur cell number
or call on 9860521352
thanks in advance
kumar brijwani
ranjithkumar1201 said:
dear all,
thank u a hundred thousand times for helping me get rid of the problem i owe u guys a lot finally got to work.
Thank u once again i dont have words to describe my joy.at ant time u want help in india count me in.
Click to expand...
Click to collapse
kumarbrijwani said:
Hi ranjith
need your help
can u drop in ur cell number
or call on 9860521352
thanks in advance
kumar brijwani
Click to expand...
Click to collapse
9036523279
feel free to sms me
i try to help you in anything i know
it would be better if you could message in Whatsapp
Sent from my MB860 using xda premium
DL here http://forum.xda-developers.com/show....php?t=1475444
error page not found
you can solve this problem....
tank's
hoaca388 said:
Soft brick .
Download moto-fastboot, and unzip to C:\moto-fastboot
DL here:http://www.android-advice.com/file-d...rix_Root_Files
Download system image for 2.3.4 and unzip to moto-fastboot folder
DL here http://www.android-advice.com/file-d...bread_4591_ROM
Download atrix oem unlock and unzip to moto-fastboot folder
DL here:http://gititbit.ch/pub/unlock.zip
open cmd and navigate to C:\moto-fastboot\
Force fastboot on phone by holding down PWR and VOL UP while inserting battery.
Type these commands:
moto-fastboot oem unlock (it will show atrix ID re-enter with ID at end of line)
when finished, then enter these commands:
moto-fastboot flash boot boot.img
moto-fastboot flash system system.img
moto-fastboot -w
moto-fastboot reboot
When it reboots, you will be back to stock, fully restored!!
I then used Pete's Motorola Tools to root my atrix.
Info and DL here http://www.psouza4.com/Bionic/
yes it did work on my atrix make sure usb debugging is on and unknown sources checked.
I then installed CWM to my Atrix
DL here http://forum.xda-developers.com/show....php?t=1475444
unzip to moto-fastboot, put atrix in fastboot mode and open cmd, navigate to moto-fastboot folder and type this:
moto-fastboot flash recovery recovery.img
Reboot and you are DONE!!!! All thats left is to find a ROM and you are good to go
Click to expand...
Click to collapse
So i just unlocked the device and Re-flashed it with mi flash tool, now the Phone is stuck at Fastboot mode.
i get this
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.001s]
finished. total time: 0.001s
Click to expand...
Click to collapse
is my bootloader unlocked?
also when i do set active a, this happens
C:\Users\user>fastboot -set active=a
< waiting for device >
I have tired every solutions i found online still no luck.
Connect the phone to pc and type in "fastboot devices" - do you see any device listed?
Also the correct command is:
fastboot --set-active=a
_mysiak_ said:
Connect the phone to pc and type in "fastboot devices" - do you see any device listed?
Also the correct command is:
fastboot --set-active=a
Click to expand...
Click to collapse
Yes i do but the command doesn't exist in fastboot please help
PS C:\tmp\platform-tools> fastboot --set active=a
C:\adb\fastboot.exe: unrecognised option `--set'
Click to expand...
Click to collapse
Also it says waiting for device it has been more then 30 minutes.
Now the Phone is rebooing at Andriod One Logo.
SpectreZ said:
Yes i do but the command doesn't exist in fastboot please help
Click to expand...
Click to collapse
Again, type it correctly.
In other words, spot the difference
fastboot --set-active=a (what I wrote)
fastboot --set active=a (what you wrote)
Do you see android/fastboot device in your device manager on the PC when you connect it to the PC in fastboot mode?
Edit: also replace fastboot.exe and adb.exe in c:\ADB\ folder as this one is being used. Or remove this folder from Windows PATHS.
_mysiak_ said:
Again, type it correctly.
In other words, spot the difference
fastboot --set-active=a (what I wrote)
fastboot --set active=a (what you wrote)
Do you see android/fastboot device in your device manager on the PC when you connect it to the PC in fastboot mode?
Edit: also replace fastboot.exe and adb.exe in c:\ADB\ folder as this one is being used. Or remove this folder from Windows PATHS.
Click to expand...
Click to collapse
I see Kedacom USB Device - Andorid Bootloader interface.
and i cannot remove the folder from C adb.
I have used mi Flash tool and while checking the log i saw boot was flashed at B so i erased the b boot useing fastboot also a
then I Reflash the B as 1st and A as 2nd the phone was able to make thru Recovery but when i restarted i went back into 0 again
SpectreZ said:
I see Kedacom USB Device - Andorid Bootloader interface.
and i cannot remove the folder from C adb.
I have used mi Flash tool and while checking the log i saw boot was flashed at B so i erased the b boot useing fastboot also a
then I Reflash the B as 1st and A as 2nd the phone was able to make thru Recovery but when i restarted i went back into 0 again
Click to expand...
Click to collapse
Are you sure that phone is in fastboot and not in recovery? What do you see on the phone screen?
You are doing too many things at once, focus on one thing and once you get it solved, move to another one. Also please provide answers to all questions, they are essential for troubleshooting.
1. Reinstall drivers and ADB - https://forum.xda-developers.com/showthread.php?t=2588979
2. Reboot phone in fastboot, connect it to the PC and type in "fastboot devices" - do you see any device connected?
Phone is now Started so what i did was.
* erased system_a
* erased system_b
also
* erased boot_a
* erased boot_b
I think the system is in B now.
(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:7
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno:35a1981490a2
(bootloader) product:laurel_sprout
(bootloader) max-download-size:804261888
(bootloader) kernel:uefi
all:
finished. total time: 0.438s
C:\Users\fahim>
Click to expand...
Click to collapse
and now the device started successfully still i think i messed up and i did everything you said.
Answer: i was on the Bunny screen Fastboot and yes " Fastboot devices " showed my device,
Can you kindly Guide me how do i factory set it? so i won't have any problem i Messed up because i didn't saw the note at StockRom in this forums where something is wrong in slots
C:\Users\fahim>fastboot --set-active-a
fastboot: unknown option -- set-active-a
Click to expand...
Click to collapse
SpectreZ said:
Phone is now Started so what i did was.
* erased system_a
* erased system_b
also
* erased boot_a
* erased boot_b
I think the system is in B now.
and now the device started successfully still i think i messed up and i did everything you said.
Answer: i was on the Bunny screen Fastboot and yes " Fastboot devices " showed my device,
Can you kindly Guide me how do i factory set it? so i won't have any problem i Messed up because i didn't saw the note at StockRom in this forums where something is wrong in slots
C:\Users\fahim>fastboot --set-active-a
fastboot: unknown option -- set-active-a
Click to expand...
Click to collapse
I guess you again did not follow given advice. You are still using old fastboot. In this case use "fastbot set_active a"
_mysiak_ said:
SpectreZ said:
Phone is now Started so what i did was.
* erased system_a
* erased system_b
also
* erased boot_a
* erased boot_b
I think the system is in B now.
and now the device started successfully still i think i messed up and i did everything you said.
Answer: i was on the Bunny screen Fastboot and yes " Fastboot devices " showed my device,
Can you kindly Guide me how do i factory set it? so i won't have any problem i Messed up because i didn't saw the note at StockRom in this forums where something is wrong in slots
C:\Users\fahim>fastboot --set-active-a
fastboot: unknown option -- set-active-aI guess you again did not follow given advice. You are still using old fastboot. In this case use "fastbot set_active a"
Click to expand...
Click to collapse
My Apologies, My Mind was rushing
Which one is the latest? can you tell me? please
Click to expand...
Click to collapse
Click to expand...
Click to collapse
1) update your ADB/Fastboot from the link I provided and use "fastboot --set-active=a"
or
2) keep what you have and use "fastboot set_active a"
_mysiak_ said:
1) update your ADB/Fastboot from the link I provided and use "fastboot --set-active=a"
or
2) keep what you have and use "fastboot set_active a"
Click to expand...
Click to collapse
Oh God thanks it worked, Can you tell me why there is A and B ? i mean 2 slots? also how do i get the device into factory fresh ?
Like the 1st time when i bought this. thank you soo much + Liked
If i use Mi Flash tool again, So am gonna be in Danger again too?
You can use MiFlash, but before flashing you need to make sure that your active partition is A (with commands mentioned before).
To restore to 100% stock:
1. set partition A as active
2. run MiFlash WITHOUT locking bootloader (or run script flash_all.bat)
3. start the phone, if everything works, move to the next step (ONLY IF PHONE WORKS)
4. run MiFlash with bootloader lock (or run script flash_all_lock.bat) or run "fastboot flashing lock"
5. after reboot, your phone should start as if it came from a factory
_mysiak_ said:
You can use MiFlash, but before flashing you need to make sure that your active partition is A (with commands mentioned before).
To restore to 100% stock:
1. set partition A as active
2. run MiFlash WITHOUT locking bootloader (or run script flash_all.bat)
3. start the phone, if everything works, move to the next step (ONLY IF PHONE WORKS)
4. run MiFlash with bootloader lock (or run script flash_all_lock.bat) or run "fastboot flashing lock"
5. after reboot, your phone should start as if it came from a factory
Click to expand...
Click to collapse
Thanks Everything is now great. However what is slot count? and what happens when it hits 0? also i locked the device via fastboot flashing lock.
It should be number of slots. 2 = boot_a + boot_b
It it hits 0, I guess you have serious problem as bootloader doesn't see any boot partition.
More info in the source code: https://android.googlesource.com/pl...otctrl/+/refs/heads/nougat-dev/boot_control.c
Hello guys. My brother's Huawei p20 Lite is stuck in a bootloop. I'm unable to access the recovery and Erecovery (tried 10 times but it just won't work.) The only thing that works is Fastboot mode and it shows this error. Can't use Hisuite because apparently this phone isn't supported to be recovered using that program. How can I fix this phone? Is it permanently bricked?
Advanced07 said:
Hello guys. My brother's Huawei p20 Lite is stuck in a bootloop. I'm unable to access the recovery and Erecovery (tried 10 times but it just won't work.) The only thing that works is Fastboot mode and it shows this error. Can't use Hisuite because apparently this phone isn't supported to be recovered using that program. How can I fix this phone? Is it permanently bricked?
Click to expand...
Click to collapse
Hello, try this way out...
1. install on your PC "Minimal ADB and fastboot" tool, in fastboot mode run command
fastboot erase userdata
and try restart the device.
Or,
2. download and use a Service ROM with an sd/card or an USB-OTG flashdrive in dload mode. Download correct Service ROM from androidhost.ru website, unpack .zip archive , find dload file in "Software" folder, and simply transfer it to the SD card, without unpacking it! (instruction can be found in ReleaseDoc folder).
Turn off your phone and flash FW using three button combo .
The first step is to determine which variant of your device you are on.
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
(The bracketed (Cxxx) is your device’s regional variant.
This number is very important in determining the correct firmware to download!).
Service ROM can be found here:
https://androidhost.ru/search.html . Type Ane- or Anne- .
For example, for build number ANE-LX1 9.1.0.278 C432) :
https://androidhost.ru/Xar
Maybe it will help you...
-Alf- said:
Hello, try this way out...
1. install on your PC "Minimal ADB and fastboot" tool, in fastboot mode run command
fastboot erase userdata
and try restart the device.
Or,
2. download and use a Service ROM with an sd/card or an USB-OTG flashdrive in dload mode. Download correct Service ROM from androidhost.ru website, unpack .zip archive , find dload file in "Software" folder, and simply transfer it to the SD card, without unpacking it! (instruction can be found in ReleaseDoc folder).
Turn off your phone and flash FW using three button combo .
The first step is to determine which variant of your device you are on.
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
(The bracketed (Cxxx) is your device’s regional variant.
This number is very important in determining the correct firmware to download!).
Service ROM can be found here:
https://androidhost.ru/search.html . Type Ane- or Anne- .
For example, for build number ANE-LX1 9.1.0.278 C432) :
https://androidhost.ru/Xar
Maybe it will help you...
Click to expand...
Click to collapse
Thanks I'm gonna give these a try and I will let you know how it goes
-Alf- said:
Hello, try this way out...
1. install on your PC "Minimal ADB and fastboot" tool, in fastboot mode run command
fastboot erase userdata
and try restart the device.
Or,
2. download and use a Service ROM with an sd/card or an USB-OTG flashdrive in dload mode. Download correct Service ROM from androidhost.ru website, unpack .zip archive , find dload file in "Software" folder, and simply transfer it to the SD card, without unpacking it! (instruction can be found in ReleaseDoc folder).
Turn off your phone and flash FW using three button combo .
The first step is to determine which variant of your device you are on.
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
(The bracketed (Cxxx) is your device’s regional variant.
This number is very important in determining the correct firmware to download!).
Service ROM can be found here:
https://androidhost.ru/search.html . Type Ane- or Anne- .
For example, for build number ANE-LX1 9.1.0.278 C432) :
https://androidhost.ru/Xar
Maybe it will help you...
Click to expand...
Click to collapse
Tried all the ADB commands and they all failed, gonna try to use the SD card method.
-Alf- said:
Hello, try this way out...
1. install on your PC "Minimal ADB and fastboot" tool, in fastboot mode run command
fastboot erase userdata
and try restart the device.
Or,
2. download and use a Service ROM with an sd/card or an USB-OTG flashdrive in dload mode. Download correct Service ROM from androidhost.ru website, unpack .zip archive , find dload file in "Software" folder, and simply transfer it to the SD card, without unpacking it! (instruction can be found in ReleaseDoc folder).
Turn off your phone and flash FW using three button combo .
The first step is to determine which variant of your device you are on.
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
(The bracketed (Cxxx) is your device’s regional variant.
This number is very important in determining the correct firmware to download!).
Service ROM can be found here:
https://androidhost.ru/search.html . Type Ane- or Anne- .
For example, for build number ANE-LX1 9.1.0.278 C432) :
https://androidhost.ru/Xar
Maybe it will help you...
Click to expand...
Click to collapse
Device won't enter dload mode either. I hold the 3 buttons but it just bootloops.
Sorry, I'm out of ideas (with the locked bootloader).
-Alf- said:
Sorry, I'm out of ideas (with the locked bootloader).
Click to expand...
Click to collapse
I'm as well, the only thing that might work is removing and placing the battery ribbon cable again but I don't have the glue to close the case. Should I still try it?
Advanced07 said:
but I don't have the glue to close the case. Should I still try it?
Click to expand...
Click to collapse
You should try it, why not.
IMO it might be the HW problem , dead memory or damaged motherboard, (fastboot commands are not working).
-Alf- said:
You should try it, why not.
IMO it might be the HW problem , dead memory or damaged motherboard, (fastboot commands are not working).
Click to expand...
Click to collapse
The fastboot commands are working but it says I don't have permission to do it or something along those lines it refuses to execute it
Advanced07 said:
Hello guys. My brother's Huawei p20 Lite is stuck in a bootloop. I'm unable to access the recovery and Erecovery (tried 10 times but it just won't work.) The only thing that works is Fastboot mode and it shows this error. Can't use Hisuite because apparently this phone isn't supported to be recovered using that program. How can I fix this phone? Is it permanently bricked?
Click to expand...
Click to collapse
Same phone and same thing happened to me. What's different is that twrp recovery works.
It all started when I unlocked the bootloader with PotatoNV. I unlocked it with the fastboot oem unlock MYUNLOCKCODE command.
Then i flashed twrp: fastboot flash recovery_ramdisk d:\twrp.img
Then whatever happened, I started seeing the error "AP_S_ABNORMAL 64" in fastboot mode, but running commands was fine.
I deleted everything by entering the codes below with fastboot mode.
fastboot erase system -w
fastboot erase userdata
Then I reinstalled twrp recovery by entering the codes below and flashed a custom rom.
fastboot flash recovery_ramdisk d:\twrp.img
fastboot flash system d:\MyCustomRom.img
Suddenly what do I see.
When I rebooted with the fastboot reboot command, twrp was constantly opening. The system would not boot at all. I was desperately doing everything I could think of. Only one thing worked. I opened emui e-recovery by pressing the volume up, volume down and power keys at the same time. It was failing there and there was only one option; I clicked restart. The system booted this time, not twrp, and after a long wait, the main installation screen came.
biorap said:
I opened emui e-recovery by pressing the volume up, volume down and power keys at the same time. It was failing there
Click to expand...
Click to collapse
it is not e-recovery, this buttons combination triggers the installation of FW by the dload method.
biorap said:
fastboot erase system -w
fastboot erase userdata
Click to expand...
Click to collapse
Use stock Recovery - Wipe cache partition & Factory reset
biorap said:
flashed a custom rom
Click to expand...
Click to collapse
How to install Treble GSI ROMs on Kirin-devices:
https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/post-84305543
-Alf- said:
it is not e-recovery, this buttons combination triggers the installation of FW by the dload method.
Use stock Recovery - Wipe cache partition & Factory reset
How to install Treble GSI ROMs on Kirin-devices:
https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/post-84305543
Click to expand...
Click to collapse
Thank you for your clarify.
Is it possible to use stock recovery when i flash a custom rom via fastboot mode? I mean; do i have to use twrp when i wanna flash a custom rom? Is it possible to use custom rom with stock recovery?
biorap said:
Thank you for your clarify.
Is it possible to use stock recovery when i flash a custom rom via fastboot mode? I mean; do i have to use twrp when i wanna flash a custom rom? Is it possible to use custom rom with stock recovery?
Click to expand...
Click to collapse
Have you read?
https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/post-84305543
after instant ubl i got notice dm-verity corruption, and i fastboot flash vbmeta still not working. any1 can help?
kaye48 said:
after instant ubl i got notice dm-verity corruption, and i fastboot flash vbmeta still not working. any1 can help?
Click to expand...
Click to collapse
Any news on this?
I also have it, have to press a button in order for it to boot, each time.
Did you try fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img when flashing vbmeta.img?
What fixed it for me was using the vbmeta file that is provided in this recovery, and apply the command.
Trying the fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img command with the original vbmeta, extracted from my ROM somehow did not do the trick.
That's strange! In the future I'd try re-downloading and extracting the image and trying again; I've found that this fixes strange bugs surprisingly often
dm-verity corrupted fix after unlocking bootloader:
Plug your phone in fastboot mode to PC and open command prompt in platform tools.
Type:
fastboot oem cdms
inrope said:
dm-verity corrupted fix after unlocking bootloader:
Plug your phone in fastboot mode to PC and open command prompt in platform tools.
Type:
fastboot oem cdms
Click to expand...
Click to collapse
Worked for me, thanks!
inrope said:
dm-verity corrupted fix after unlocking bootloader:
Plug your phone in fastboot mode to PC and open command prompt in platform tools.
Type:
fastboot oem cdms
Click to expand...
Click to collapse
Worked for my Xiaomi Redmi 10A. Thank you.
inrope said:
dm-verity corrupted fix after unlocking bootloader:
Plug your phone in fastboot mode to PC and open command prompt in platform tools.
Type:
fastboot oem cdms
Click to expand...
Click to collapse
Bro Thank you VERY VERY Much it Fixed because i unlock bootloader and i got the error dm verity even install img and fastboot oem cdms worked! | and becuase 168 hours i can't wait i install different exe file now it fixed! thank you | i make this account right now
to thanks | im from philippines
Hi i have an redmi note 11s it was showing dm-verity corruption earlier and then now it just wont boot at all not even to fastboot or recovery.. anyways i still can save this phone? its only 1 year and 1 month old...
How is that? Can anyone show me a tutorial please? My mom's xioami is showing this error and I don't know how to fix It, I have only found YT videos in Idian but nome of It worked.
inrope said:
dm-verity corrupted fix after unlocking bootloader:
Plug your phone in fastboot mode to PC and open command prompt in platform tools.
Type:
fastboot oem cdms
Click to expand...
Click to collapse
Could you show me how you did It step by step please? I would really appreciate it
malex174 said:
Worked for me, thanks!
Click to expand...
Click to collapse
JJLechadores said:
Bro Thank you VERY VERY Much it Fixed because i unlock bootloader and i got the error dm verity even install img and fastboot oem cdms worked! | and becuase 168 hours i can't wait i install different exe file now it fixed! thank you | i make this account right now
to thanks | im from philippines
Click to expand...
Click to collapse
Hi, I'm also from the philippines. can you help me? I'm having the same issue
For anyone facing this issue on Realme devices, or any other devices, here's how you can solve it without resetting or wiping out your data:
Steps:
Turn off your phone.
Press the volume down + power button.
Release both buttons once the Realme logo appears.
Select the recovery mode option.
Choose your preferred language.
Select the reboot option.
By following these steps, you should be able to resolve the issue without losing any of your data.