Database Develop

Bricked milestone stuck on bootloader flashed bootloader again but no use

please help me i bricked my milestone while doing 1% battery step.now whats happening is that phone is automatically starting in bootloader and error is coming err:a4,35,36.whenever i try to flash my sbf :crying::crying::crying::crying::crying:my phone switches on but whenever i reboot it,it again gets stuck in the bootloader please help me please even tried to flash the bootloader again but no use

please help people..

Is this first time are you trying to Root, Unlocking bootloader?
If u are using Milestone with already unlocked bootloader then u can directly boot to Open recovery and flash your required ROM.
If u are now flashing for the first time refer instructions from link http://forum.xda-developers.com/showthread.php?t=983516
You have to flash the correct sbf file.
? Have you installed Open recovery ? copied update.zip file in root of SD card or /SDCARD/update.zip
1. Press Camera button + power On
2. You will be asked either to install Open Recovery - update.zip file. or if u have already installed OR then it should directly take you to OR.
3. Flash the required ROM.
d.o.doubleg said:
please help me i bricked my milestone while doing 1% battery step.now whats happening is that phone is automatically starting in bootloader and error is coming err:a4,35,36.whenever i try to flash my sbf :crying::crying::crying::crying::crying:my phone switches on but whenever i reboot it,it again gets stuck in the bootloader please help me please even tried to flash the bootloader again but no use
Click to expand...
Click to collapse

[Q] need some serious help with return to stock

hi all,
sorry to sound like a complete idiot in advance !
I have been trying for over a month now to find some way to return my phone to stock so I can get the new ota update but im just having no luck !
I have tried everything to unroot , relock boot loader, and return to stock, I can successfully unroot, successfully relock the boot loader but cannot update OTA everytime I download the ota and allow the phone to start update process the phone boots into bootlaoder and a new line appears in the normal messages **** security warning*** when this happens I loose recovery and the phone hasn't updated. I then have to re-unlock the bootloader to then flash a recovery.
I cant flash RUU as there isn't an RUU available for me, H3G_001 , I have tried the suggested CWM nandroid backup, but this fails half way through something to do with android_secure
I cant seem to get the phone to successfully grant s-off to try the change cid method, I have tried to do this using HTC one kit by hasoon but no luck,
if anyone could please help it would me much appreciated
regards
okz19

Probably you don't have the stock rom or the recovery, because the secure warning come out when you aren't fully stock..

Look on this site: http://www.htc1guru.com/downloads/stock-rom-downloads/
Mine One works now fine and i have update to the latest OTA.

Justin2003 said:
Look on this site: http://www.htc1guru.com/downloads/stock-rom-downloads/
Mine One works now fine and i have update to the latest OTA.
Click to expand...
Click to collapse
Is better link to XDA

still stuck!
hi all as you can probably tell form the age of this topic, I have been stuck for a while !!! (11 October ! )
I am still having problems trying to get the new update 2.24.771.3
my phone is carrier locked to three uk
it is unrooted
custom recovery cwm touch
bootloader unlocked / tampered
I understand I need stock recovery and to lock bootloader
I don't have stock rom
my problem is as follows, my phone has been telling me for atleast 4 months now that I have a software update, when I click it it restarts takes me to cwm recovery verifys install then gets stuck on cannot mount data ....
I understand I need to flash stock recovery, I have tried to do this using the "all in one kit" however when I click flash my own recovery, (phone reboots into bootloader) I then proceed to select the stock recovery.img the cmd box then hangs "waiting for device" I am then alerted by my computer that the usb device has malfunctioned. ( I am on windows 8 and have turned of signature verification)
I cannot use the supposed simple method of RUU as there isn't one available for my stupid network!!
I have tried to use a cwm recovery image, this usually starts then spits out android_secure is missing.
yes I do have a hammer ready to hit the phone with, but just before I do this is there ANYONE with any last tips to help me, because ive just about had enough with this stupid phone !
the phone has 24 hours left to live, can you save its life ?
thanks in advance for any help.

1. You cannot install an OTA with a custom recovery.
2. I've encountered a CWM bug having to do with .android_secure. There's a hidden folder in /sdcard that caused it, I don't remember whether this file is ".android_secure" or another. You can probably wipe the sdcard before restoring the backup. If that fails, you can probably manually restore the backup with ADB (this will be hard).
3. If you want to install the custom recovery, boot to the fastboot and use USB to install the recovery. Don't use a toolkit because they're useless when anything goes wrong.

Trying to get back to stock rom

Hello,
Tried rooting my phone with no prior experience. Worked, but eventually I got to where the phone wouldn't boot past splash screen (logo came up, then screen went black while backlight is on and didn't respond to stimuli until battery was removed). Possibly resulted from a build.prop file problem. Did get into boot though, so I fixed that problem by installing a cyanogen rom from a zip file using twrp recovery. I didn't want a custom mod though since I'm used to the look and feel of the 4.0.3 ICS I had, and the cyanogen doesn't seem to have google play so I can't even download anything (original purpose of rooting was to get incompatible apps by spoofing via build.prop file). Currently trying to get back to stock. Unfortunately I didn't make a nandroid backup of the system before the problem occurred, hence I have no backup to flash.
What I tried:
1. Use the official HTC 4.0.3 RUU .exe to upload to the phone. Unfortunately HTC Sync doesn't see this phone, even though I have the correct drivers installed.
2. Attempted to use twrp recovery to install the rom.zip extracted from the RUU directly, the same way I successfully installed the cyanogenmod rom. Failed, claiming it's unable to open zip. The .zip file was checked for integrity and returned by an archiver app.
3. Tried to use these commands from the cmd with phone connected to install the .zip from fastboot:
fastboot erase cache
fastboot oem rebootRuu
fastboot flash zip rom.zip (rom.zip being the functional file of the stock rom)
Failed, saying it's not allowed. Tried it with both locked and unlocked bootloader, no difference.
4. Unzipped the file and tried to flash the system.img file directly, but that failed with a "data length is too large" error.
5. My recovery being twrp 2.1.1, tried looking for altenatives. Can't find any links to download the WCX recovery, but I found several for newer twrp versions, including 2.3.1.0 and 2.6.3.0 which I tried downloading flashing. After flashing the phone got stuck at the cyanogenmod loading logo and wouldn't boot further, and the recovery itself didn't work, just showed the HTC splash, turned black, then booted again normally, getting stuck at the cyanogen logo. Same thing for the 2.6.3.0 version, so I reflashed the original 2.1.1, at which point I can get into recovery but the phone is still stuck at the cyanogenmod during normal boot. At this point I installed the original cyanogenmod .zip from recovery and now at least the phone boots up normally. Still need to get stock back somehow.
Out of ideas and exhausted from this. Any help would be appreciated. Perhaps anyone has a working stock 4.0.3 rom for the Vivid, nandroid backup, etc., or any other ideas. Thanks for reading.

Oh crap...
OK... First... Stock rom can be found in development... Most of the roms there are stock... Read the OP... It'll tell you...
Second... You should use TWRP 2.5.3.0 or something like that I forget...
Third... When you tried the ruu... Did you relock your bootloader...
Side note... Could you get your phone to show up with 'fastboot devices'

can't unlock bootloader critical and other things..

ok guys so my dad has bricked his nokia .8.. i managed to get Twrp working again. and that's about it.. the bootloader is unlocked but i cant can't unlock "bootloader critical" it says something like " (remote command not allowed)" when i check the device info it says bootloader is unlocked but bootloader critical is not.. iv tried flashing via the ost but it says i need to unlock the critical bootloader..
another problem is that i cant flash in twrp. it says invalid zip file or something...
has anyone got a Twrp Backup they could upload so i can try and get this thing working again? or a zip i can flash via twrp?
cheers.

Did you do "fastboot flash unlock <path to unlock.key>" before trying to execute "fastboot oem unlock_critical"?
Did you maybe have an unlock key that was generated through the unofficial unlock (every build before august 2018) and are now on a newer build that supports only the official unlock?
If you can't manage to unlock the bootloader to critical, get some stock boot image (I have some at https://bit.ly/nokia-nb1), flash that to your active boot partition in fastboot (overwrite TWRP with it), then boot into stock recovery and sideload a full OTA package (which will restore all partitions that might be corrupted). All 1.5 GB files you can see in the OTA folder at the link I posted are full OTAs and will work.

ok so just an update i managed to get a rom on there, i found the right key and did the unlock all over again.. all booted ok, problem now is that i have no signal... i cant send any mssgs or phone calls. i tired to update the smsc. via this *#*#4636#*#*. and going phone info etc, but it says update error, iv also tried the encoded number for ee, but still says update error. i can put the sim card into another phone and it will send messages etc, i did read that i could update the smsc on a diffrent phone then put it back into the nokia and it will work, but it did not for me...
again there was another video showing how to fix this via backing up the firmware folder on rom then replacing with the one that dose not work . but ... i dont have a rom that works lol . iv also tried to install diffrent roms or systems and still the same problem.. i use the NOST tool. to update the firmware
any advice????
also this is his account hence a diffrent account name lol
cheers

SAMSUNG NOTE 8 N950F (XSP - Singapore Region) WONT BOOT INTO SYSTEM!! HELP!!

hi guys, im lost and desperate need help right now
its been 4 days im looking for solution but no avail
please i need help to make my device back to normal again
device : Samsung Note 8 (XSP - Singapore Region) running One UI 1, Android 9. oem unlocked.
so here is the stories,
3 days ago, 22 Dec 2020.
i did factory reset on my device, and reboot
after that, my device lost the network, it detect my sim card but cant connect to network. signal lost.
i tried to reboot like usuall but still, no network available. lost the signal
but i can connect to wifi.
and i reboot it again, suddenly stuck at samsung logo
at first i thought this is easy just need to flash it with stock firmware
and i did, i download the stock firmware from sammobile, XSP - Singapore region.
with BL, CP, CSC, AP file, repartition not ticked. only tick the Auto Reboot and F. Reset time.
i choose the CSC file not HOME_CSC. so everything went well. PASS! green light in odin.
successfully flash my device, but weird, it is still wont detect any network or signal. i tried to automatically find network operator but it says "unable to connect" i tried everything and it says "NO NETWORK"
i did checked my imei , and its safe, its not blocked. but why my device still wont detect my sim card
and the i tried to reflash and flash and flash it again, several time hoping it will detect any network from my sim card after flashing but no avail
and then at the night, flash at 6th time, my device giving me more problem.
suddenly stuck at samsung logo bootloop. i went to recovery state, its says :
"E: FAILED TO MOUNT /EFS (INVALID ARGUMENT)
DM VERITY ERROR" stuff like that
damnn what problem again this time
im frustated already
and i flash it again with Pixel Experience rom hoping the problem will went away, but still , same results. "NO NETWORK"
i look it up in Settings - About - Status - Sim Card Status , its shown "DISCONNECTED"
my imei still there but just wont connect to network.
and then i tried to re-flash it again with stock firmware and again went straight into bootloop. with broken efs etc some****
im so mad and frustated, the problem keeps coming.
and then i found a temporary solution from @bluecub1st thread about the same problem :
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The following is a guide for repairing failed to mount efs and dm-verify fail (drk error)
We finally did it ~~~
Warning - We will not take any responsibility for your device. Follow the steps at your own risk. If your device is Knox 0, This guide would convert it into Knox 1 due to TWRP. For solutions that does not convert to knox 1 check out payed remote solutions. Everything on your device will be reset, including efs partition. You will need backup of efs.
Test on N950F binary 4 may work on other exynos models comment below if it worked for other samsung devices.
Problem Detail -
Bootloop with samsung stock firmware boot logo.
Recovery error E:Failed to mount /efs (Invalid argument) or dm-verity verification failed...
Device cannot boot into Factory binary or Stock Rom
Actions that could cause this problem -
Flashing a non-signed efs.img by odin
Corrupt flash of efs partition.
Note - Must have efs backup for device to work (very important)
Any error that cause bootloop would show in recovery required if
Files Required
Latest Odin (recommend 3.13)
Working Stock firmware and Combination file (same binary as bootloader)
PC
Winrar or 7zip etc
Solution for efs failed bootloop-
Extract Stock firmware AP file (rename .md5 to .tar)
Rename dqmdbg.img to efs.img (or smallest image must be smaller than 8000 KB). Extract Dqmdbg.img.lz4 so it’s just “Dqmdbg.img” and then rename it to efs.img and put that one in a tar. Other option is downloading a file that’s already made this way if your bootloader is binary 4, Saves you trouble of extracting / renaming: http://www.mediafire.com/file/589wucja9rk2v8f/efs.tar/file (if you download this file just move onto number 3)
Add file new efs.img into tar archive.
Flash tar as AP file in odin + download mode
Reboot download mode
Flash Combination with odin + nand erase option on Edit: suggest you to flash stock rom first and oem unlock, don't need to wait for 7 days if imei is 0000 skip combination step
Device Should boot into Factory binary
Use IME to restore imei using *#06# (or imei 0000 in stock rom) Edit: This step is not required if efs backup is restored successful
Your device should have dm-verify failed in recovery due to drk error
Continue drk bypass for dm verify error below to continue
Solution for dm-verify error (also known as drk bypass - but temporary read note)-
Extract Stock firmware AP file
Make a copy of boot.img and delete recovery.img
Note - if files is boot.img.lz4 format change name to recovery.img.lz4
Rename boot.img copy to recovery.img
Add all the files (including other files extracted) to tar.
Flash Modded AP file with BL, CP, CSC (nand erase not required)
The phone will boot into stock firmware
Note- cannot reboot, will stuck at dm-verify error again and need to flash modded AP again.
Wait 7 days to oem unlock phone or use 7 day bypass by changing dates (not always work, keep trying, don’t reboot, worked for Samsunguser932 Edit: Imei must be 0000)
Edit: oem unlock will fix drk - if not you must follow next step
Once oem unlock flash TWRP and restore efs backup Edit: if you haven't fixed imei fix now by *#06# with combination file
Flash stock firmware once again by odin (stock, not modded)
Done - phone is back to normal
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
but at my case , the solution still failed,
yes it did success boot back into the system but still my network is still missing.
and he says restore with efs backup but he didnt attach the file to download the efs backup, how can i continue that step?
so i skip that step and just went to reflash it with stock firmware and the problem came again, it stuck in bootloop.
with efs broken ,
anyone here can share your efs backup ?
please i need it
im using samsung note 8 n950f XSP Singapore region
will appreciate your help a lot. thanks a lot

....................