Related
Hi dose somebody now how to remove this brick i tried everything ?
and this dose not worked http://forum.xda-developers.com/razr...5?goto=newpost
I think when you have the service code error there is nothing you can do.
But you still get into bootloader, correct?
Have you tried manually flash the recovery / gpl / motoboot etc. once at a time?
If you cant get into bootloader anymore, try this, but only then
dagoban said:
I think when you have the service code error there is nothing you can do.
But you still get into bootloader, correct?
Have you tried manually flash the recovery / gpl / motoboot etc. once at a time?
If you cant get into bootloader anymore, try this, but only then
Click to expand...
Click to collapse
I can not get to bootloaderI tried every thing its stuck on Service Required code corrupt message.
What you mean about manually flash the recovery - you mean over the bootloader fastboot flash recovery recovery.img ?
No i can not, can only connect as MEDFIELD
miky03 said:
I can not get to bootloaderI tried every thing its stuck on Service Required code corrupt message.
What you mean about manually flash the recovery - you mean over the bootloader fastboot flash recovery recovery.img ?
No i can not, can only connect as MEDFIELD
Click to expand...
Click to collapse
Sorry, forgot to include the link: http://forum.xda-developers.com/razr-i/help/help-unbrick-completely-unmodified-razr-t2980659
If you cant get into the bootloader, it means you are not into fastboot mode, which means you will not be able to flash anything (bootloader, recovery, system partition)
If this is the case, then do this http://forum.xda-developers.com/razr-i/help/help-unbrick-completely-unmodified-razr-t2980659
If you successfully flash it but still your phone is not working, then you can throw away your phone, it is bricked beyond good and evil. Happened to me, too, not even Motorola could repair it then. If you are still in warranty, send it to Moto and you get a new device.
dagoban said:
Sorry, forgot to include the link: http://forum.xda-developers.com/razr-i/help/help-unbrick-completely-unmodified-razr-t2980659
If you cant get into the bootloader, it means you are not into fastboot mode, which means you will not be able to flash anything (bootloader, recovery, system partition)
If this is the case, then do this http://forum.xda-developers.com/razr-i/help/help-unbrick-completely-unmodified-razr-t2980659
If you successfully flash it but still your phone is not working, then you can throw away your phone, it is bricked beyond good and evil. Happened to me, too, not even Motorola could repair it then. If you are still in warranty, send it to Moto and you get a new device.
Click to expand...
Click to collapse
I tried everything my razr i still Hardbricked
now i want to tray this method:
set PACKAGE_DIR=unbrick
set FWDNX=--fwdnx %PACKAGE_DIR%\dnx
set FWIMAGE=--fwimage %PACKAGE_DIR%\ifwi
set OSDNX=--osdnx %PACKAGE_DIR%\dnx
set OSIMAGE=--osimage %PACKAGE_DIR%\motoboot
unbrick\xfstk-dldr-solo.exe %FWDNX% %FWIMAGE% %OSDNX% %OSIMAGE% --verbose
Question where i can get this files from (dnx, ifiw, motoboot) ?
I had CM11 before then downgrade to ICS 4.0.4. then used wrong script for rooting then got "Service Required code corrupt message".
miky03 said:
]
Click to expand...
Click to collapse
Please also don't post the same question in several threads, we try to keep it as clean as possible here
I have a sony xperia z c6603 , it was never unlocked from the start but it worked very fine on its original firmware, android 4.1.2. But then someone flashed a c6602 android 4.1 on it and now the IMEI is corrupted and it restarts every 9.3minutes.
It says bootloader unlock allowed: Yes which I guess means the bootloader is locked and can be unlocked, but since IMEI is corrupt, i cant request for unlock code from sony or use fastboot.
My only other option is the famous flashtool. I have three issues with flashtool.
1. I already downloaded the correct firmware and preparing to flash, so I click on the flash icon and start flash (Using Androxyde flash tool). It goes through the normal process and then an empty device selector screen comes up, with no option but to cancel. and when i cancel, it says "loader not found for this device"
2. Okay, after step 1, i am thinking "maybe i have to unlock the bootloader first" so i click on the BLU button and connect the device in flash mode, it starts and the empty device selector screen comes up again, once i cancel, it says "your device can not be officially unlocked"
3. So i did a little bit of digging around on here more and found that i have to update xflasher.jar to beta6, and so i did and flash tool started as "androxyde and bin4ry flash tool" .Only problem is when i click on the flash icon and choose flash mode, nothing comes up, i cant get into flash mode. but I can get into every other thing like fastboot mode and BLU
Please if you think you have an idea on how to solve this problem, please reply. I cant afford a new phone and I would also like to know if my phone can be repaired too, I also dont have a lot of time to waste trying to repair it.
try to reinstall flashtool after deleting it first .. install fastboot and flashmode drivers and drivers for ur device from drivers folder in flashtool folder.. disable any antivirus and any app that could interfere and unplug any usb device ... try to flash with flashmode
---------- Post added at 12:39 AM ---------- Previous post was at 12:35 AM ----------
mordr3d said:
I have a sony xperia z c6603 , it was never unlocked from the start but it worked very fine on its original firmware, android 4.1.2. But then someone flashed a c6602 android 4.1 on it and now the IMEI is corrupted and it restarts every 9.3minutes.
It says bootloader unlock allowed: Yes which I guess means the bootloader is locked and can be unlocked, but since IMEI is corrupt, i cant request for unlock code from sony or use fastboot.
My only other option is the famous flashtool. I have three issues with flashtool.
1. I already downloaded the correct firmware and preparing to flash, so I click on the flash icon and start flash (Using Androxyde flash tool). It goes through the normal process and then an empty device selector screen comes up, with no option but to cancel. and when i cancel, it says "loader not found for this device"
2. Okay, after step 1, i am thinking "maybe i have to unlock the bootloader first" so i click on the BLU button and connect the device in flash mode, it starts and the empty device selector screen comes up again, once i cancel, it says "your device can not be officially unlocked"
3. So i did a little bit of digging around on here more and found that i have to update xflasher.jar to beta6, and so i did and flash tool started as "androxyde and bin4ry flash tool" .Only problem is when i click on the flash icon and choose flash mode, nothing comes up, i cant get into flash mode. but I can get into every other thing like fastboot mode and BLU
Please if you think you have an idea on how to solve this problem, please reply. I cant afford a new phone and I would also like to know if my phone can be repaired too, I also dont have a lot of time to waste trying to repair it.
Click to expand...
Click to collapse
try to install a newer version of flashtool ...
I need to lock my bootloader to do an exchange at T-Mobile. I have 20R stock flashed, but it still says custom bootloader upon boot, how do I relock it safely?
I read that "fastboot oem lock" will work, but will brick it if I don't do it perfectly. Any advice on what to do?
TechGuruGJ said:
I need to lock my bootloader to do an exchange at T-Mobile. I have 20R stock flashed, but it still says custom bootloader upon boot, how do I relock it safely?
I read that "fastboot oem lock" will work, but will brick it if I don't do it perfectly. Any advice on what to do?
Click to expand...
Click to collapse
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
I'm terribly sorry if bumping is not ok.
Thought it wasn't worth making a new thread, since my post is about the one above.
Has anybody actually tried these steps above? (Since every other thread mentioning this says it's a one-way only thing..)
Does locking the bootloader means also loosing the custom recovery? (I'd expect that, but asking to be sure)
Does it return the phone to it's original state? (ie. before one unlocked the bootloader, or there are some differences?)
Does it also means I would be able to get official OTA updates and so on? (since with a custom recovery, that's not possible)
Thanks in advance.
Yes, it does work. I did it, worked perfectly. Yes it does return your device to it's original state. Just make sure the stock ROM is flashed and all should be well. I didn't try, but I see no reason why it wouldn't let you get OTA updates from T-Mobile. Let me know if you need help.
Nadeox1 said:
I'm terribly sorry if bumping is not ok.
Thought it wasn't worth making a new thread, since my post is about the one above.
Has anybody actually tried these steps above? (Since every other thread mentioning this says it's a one-way only thing..)
Does locking the bootloader means also loosing the custom recovery? (I'd expect that, but asking to be sure)
Does it return the phone to it's original state? (ie. before one unlocked the bootloader, or there are some differences?)
Does it also means I would be able to get official OTA updates and so on? (since with a custom recovery, that's not possible)
Thanks in advance.
Click to expand...
Click to collapse
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.
raptorddd said:
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.
Click to expand...
Click to collapse
Thanks both for replying.
And no @raptorddd , I did not mean that.
Your post is the only mentioning that locking the bootloader is possible, while all the other similar threads have ony people saying otherwise / it's not possible. I guess a slightly doubt is legit to have, don't take it wrongly
raptorddd said:
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
Click to expand...
Click to collapse
I have follow this instructions and now it giving me and error. Any fix??
WARMANH811 said:
I have follow this instructions and now it giving me and error. Any fix??
Click to expand...
Click to collapse
What error?
TechGuruGJ said:
What error?
Click to expand...
Click to collapse
Secure booting Error!
Error code: 1003
MODIFIED ! !
WARMANH811 said:
Secure booting Error!
Error code: 1003
MODIFIED ! !
Click to expand...
Click to collapse
are you sure you have h811.? i did not get that error ive tried this twice..
i remeber getting an security boot error on LG G2 i fix by flashing firmware .. so maybe KDZ could help..
if not am not sure then search for that error and find out how to fix.
raptorddd said:
ive done it .. it works. it will build dalvik once it reboots.
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
Click to expand...
Click to collapse
My H811 T-mobile phone needs service. It has original 20v software version. It is unlocked with TWRP and rooted. Can I use this method? Do I first have to downgrade software to some other version? Will this method also take out TWRP and root or do I still have to take them out before doing this? How? Please help.
joecandle said:
My H811 T-mobile phone needs service. It has original 20v software version. It is unlocked with TWRP and rooted. Can I use this method? Do I first have to downgrade software to some other version? Will this method also take out TWRP and root or do I still have to take them out before doing this? How? Please help.
Click to expand...
Click to collapse
no need to downgrade. to remove root and any trace if phone works. is to use KDZ then once it boots into system do the lock procedure. so it locks and the small white letter are removed. this way its like stock rom and recovery and the above commmands will make bootloader locked. and sent to repair. if bootloops try the freezing method.
Used on an LG Aristo that has Cyanogen and it worked
raptorddd said:
ive said ive done it. on the above instructions you dont beleive.??
i think you loose the twrp phone doesnt show unlocked bootloader message did not check recovery but it must revert t stock one.. not sure about OTA since am not in tmobile network.
you dont need OTA. you can always download KDZ and flash it with LGUP.
and stay uptodate.
Click to expand...
Click to collapse
This was the only one i found that didnt brick my phone and trust me ive bricked and unbricked this phone many times
When you use the fastboot command to lock back your bootloader, the phone doesn't revert automatically to the stock recovery and actually that is partly the reason why it bricks and other main reason is that changes made to bootloader to obtain root brick the phone. before you relock bootloader, if you have SuperSU (in-app menu option) or Magisk (uninstall zip file), use their respective methods to unroot the phone, then use twrp to flash .image file of stock recovery to recovery partition then use the fastboot command to lock the bootloader. Even then it may or may not work because if whatever method the phone uses to check the integrity of bootloader and/or recovery, such as md5, if it doesn't match, the phone will still brick. Since all your data on phone will be erased regardless as soon as you lock the bootloader, i personally just fastboot lock the bootloader, remove battery to power down, use the volume up and plug usb cable in from pc to put phone in download mode and just use LGUP (uppercut) if have kdz file already, which i do, i just let LG Bridge download the file, find it in programs folder and copy it to another location before LG Bridge deletes it --OR-- just use error recovery option in Software Update tab in LG Bridge as both LGUP and LG Bridge will detect the phone in download mode even if it is bricked.
By the way, I have used both methods above dozens of times without any issues, someone above who mentioned phone boot-looping because of locking the bootloader, it is boot-looping not because of hardware flaw which was widespread in LG G3 but a software issue (phone boots up, doesn't find the software configuration it is looking for and just restarts) and they are not the same issues, no need to freeze the phone, won't help.
the method works, but no OTA from T-Mobile. "verification problem".
When I try to "adb reboot bootloader" I get "security error".
If I try reboot recovery, TWRP is definitely not there.
Just want to update from20Q to 20X.
Any help would be appreciated.
metropical said:
the method works, but no OTA from T-Mobile. "verification problem".
When I try to "adb reboot bootloader" I get "security error".
If I try reboot recovery, TWRP is definitely not there.
Just want to update from20Q to 20X.
Any help would be appreciated.
Click to expand...
Click to collapse
The above points to you not giving permission possibly because either you missed the permission pop-up or selected option that didn't allow permission.
Can anyone help me?
When i unlock bootloader on my lg velvet 4g the fingerprint stop working so i want to relock. But when i put this on cmd "adb reboot bootloader" it only restarts my phone. Doesnt shows me the bootloader menu it only restarts normaly
Lukasz23 said:
Can anyone help me?
When i unlock bootloader on my lg velvet 4g the fingerprint stop working so i want to relock. But when i put this on cmd "adb reboot bootloader" it only restarts my phone. Doesnt shows me the bootloader menu it only restarts normaly
Click to expand...
Click to collapse
managed to solve?
Hello, I rooted, and installed custom recovery on my 1+3t. And the new update came out. I decided to give it a shot. Long story short. I locked my bootloader. And when I try to boot it up. It shows logo for one second, vibrates, and is stuck in that bootloop. I can get into recovery, and fastboot, but bootloader is locked. Any ideas?
Use recovery unbrick tool.
And don't lock your bootloader when you're going to flash any kind of mod, like Magisk.
You can unlock bootloader if you have activated oem unlock and usb debugging in the developer option. Then you are good to go for custom recovery..
You should never re-lock your bootloader after you flash anything not signed by OnePlus. Your device can never be booted up and only can be fixed if you use the unbrick tool by Qualcomm.
thes3usa said:
You should never re-lock your bootloader after you flash anything not signed by OnePlus.
Click to expand...
Click to collapse
My thoughts exactly.
To the OP, you don't need to lock the bootloader to update this device. And you should never lock the bootloader with mods on the phone (TWRP, root, etc.).
Good rule of thumb, is to read up before doing an update like this. Would have saved you a lot of hardship, as all the info is here on XDA for those that care to search and read.
Hey,
My Phone: HUAWEI P9-EVA-L09
My Problem: recovery mode stucks after TWRP install at
!
Your device has been unlocked and can't be trusted.
To learn more, visit:
"HERE IS A LINK"
Your device is booting now...
Click to expand...
Click to collapse
i want to fix this bring it back to original ore to TWRP hope anyone can help
Greats Kralle Fuchs
FIX
Found the Problem!
The Device say's its unlocked but it wasnt so i unlock it second time and it just reboots after second unlock in to the TWRP.
Maybe it will help someone
You couldn't flash TWRP if you didn't unlock bootloader - and the phone warns you that bootloader is unlocked
If you want to get rid of the warning, you must re-lock bootloader, but it will trigger factory reset
Btw, enable Development options and check if OEM Unlocking is enabled
And in Fastboot, check does it show Bootloader and FRP unlocked