Unbricking A100 - Acer Iconia Tab A100

As anxious as I am an ass after unlocking the bootloader and install cwm ics wanted to return to the locked bootloader with cwm recovery and now "boot not verified" and I can not change or A200 for fastboot bootloader "operation not permitted" and hoped APX in my androidboot-SerialNo with euu (APX trought flash mode) of the page vache and is worthless and this time the sat not swallow it becomes clear that this manipulated the boot and recovery so do not do any help will be grateful to and for many people with this problem for various reasons
health

peporras said:
As anxious as I am an ass after unlocking the bootloader and install cwm ics wanted to return to the locked bootloader with cwm recovery and now "boot not verified" and I can not change or A200 for fastboot bootloader "operation not permitted" and hoped APX in my androidboot-SerialNo with euu (APX trought flash mode) of the page vache and is worthless and this time the sat not swallow it becomes clear that this manipulated the boot and recovery so do not do any help will be grateful to and for many people with this problem for various reasons
health
Click to expand...
Click to collapse
So wait you can't use fastboot?, because if you can try flashing our bootloader and then try the unlockboot loader technique.

You can not because the bootloader Original ics A100 is blocked in fastboot mode screen says "operation not allowed in locked mode" or maybe not appropriate commands

As far as I understand it, Your only hope is using fastboot to flash the unlocked bootloader again. I'm not sure why did you do this, since using custom recoveries require either an unlocked bootloader or some other way to bypass the security.

peporras said:
As anxious as I am an ass after unlocking the bootloader and install cwm ics wanted to return to the locked bootloader with cwm recovery and now "boot not verified" and I can not change or A200 for fastboot bootloader "operation not permitted" and hoped APX in my androidboot-SerialNo with euu (APX trought flash mode) of the page vache and is worthless and this time the sat not swallow it becomes clear that this manipulated the boot and recovery so do not do any help will be grateful to and for many people with this problem for various reasons
health
Click to expand...
Click to collapse
hello peporras, am i understanding correctly that you are able to access fastboot mode? if this is correct, you should be able to access adb. what exactly did you do to get your tablet where it is now? what exactly is happening when you turn on the tablet? were you rooted and did you have an unlocked bootloader when you got in this situation? let me know and i will do what i can to get you back up and running as soon as possible. good luck

so you flashed the a100 bootloader back to it? Are you able to boot into android? If so, I don't see why you can't install the a200 bootloader like you did before (assuming your rooted). Once you do that, you can unlock it with fastboot.
Sent from my SPH-D710 using Tapatalk

oneovakindoldys2 said:
hello peporras, am i understanding correctly that you are able to access fastboot mode? if this is correct, you should be able to access adb. what exactly did you do to get your tablet where it is now? what exactly is happening when you turn on the tablet? were you rooted and did you have an unlocked bootloader when you got in this situation? let me know and i will do what i can to get you back up and running as soon as possible. good luck
Click to expand...
Click to collapse
Ics because it has the last filtered root vache + + wm, if you boot normally in the upper left "verified boot failed" if I boot in recovery "recovery verified failed" and if you can boot into fastboot "bootloader v0.03.11-ICS: STARTING astboot download usb protocol protocol "and is another option that erases user data, I can not access ADB in any way I have a dmsg.test I drew a serial.no when used to work but not APX EEU-FLASH and a pair backup that I did with cwm when it worked I'm sure some way to restore it to and
regards

Euclid's Brother said:
so you flashed the a100 bootloader back to it? Are you able to boot into android? If so, I don't see why you can't install the a200 bootloader like you did before (assuming your rooted). Once you do that, you can unlock it with fastboot.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Well do not know why I did it maybe because I'm restless and try to leave the factory but now I have a nice paperweight bad mark

that is amazing over 430 visit of this help request without any answer please give me a Proposal
thanks

Related

Can't manage to unlock my nexus bootloader succesfully

Hello
I did accidentally have a power failure on my computer when flashing version 4.0.4 to my Galaxy Nexus and the phone keeps booting on recovery menu automatically.
I have tried to flash different version using fastboot and Odin but always get an error saying my bootloader is locked use "fastboot oem unlock"
When try to unlock using the command the phone displays a selection screen asking to unlock the bootloader YES/NO, If I select YES the fastboot line returns the following error FAILED (remote: Unknown Partition) and the bootloader keep locked.
I have tried a thousand times without success and I am not able to utilize any firmware because is not permitted until I manage to get the bootloader finally Unlocked.
Pls help
Thanks
How about you
a) Flash an official rom via stock recovery and try it then
b) Ask this question in the Questions and Answers section instead of the Development section because I don't see any development relevant information in this post...
gevenerof said:
Hello
I did accidentally have a power failure on my computer when flashing version 4.0.4 to my Galaxy Nexus and the phone keeps booting on recovery menu automatically.
I have tried to flash different version using fastboot and Odin but always get an error saying my bootloader is locked use "fastboot oem unlock"
When try to unlock using the command the phone displays a selection screen asking to unlock the bootloader YES/NO, If I select YES the fastboot line returns the following error FAILED (remote: Unknown Partition) and the bootloader keep locked.
I have tried a thousand times without success and I am not able to utilize any firmware because is not permitted until I manage to get the bootloader finally Unlocked.
Pls help
Thanks
Click to expand...
Click to collapse
Try using the Gnex Toolkit posted on the development page as a sticky.
since u can't use fastboot (and the toolkit is useless in this case), i think u should try odin
THIS IS NOT DEVELOPMENT
Do not post question threads here
Read forum rules before posting threads
Thread moved
FNM
First of all, use ANY toolkit (Mine's in the description ^^)
Then unlock your bootloader (Open cmdthe type:
Code:
fastboot oem unlock
You'll need ADB/fastboot drivers installed, though...)
There's no point using a toolkit, how it sounds to me is you somehow messed up a partition when flashing the update.
As someone already said try flashing an ota update through the stock recovery (if you have stock recovery)
It was probably the bootloader that got messed up when your power went.
Try flash a new bootloader too, see how that goes.
Fastboot flash bootloader filename.img
I am having the exact same issue. Trying to flash, format or dare i even say erase won't do anything to the bootloader, trying to access recovery on mine it says failed, trying to unlock the bootloader through oem unlock, prompts the failed : remote unknown error code. :S
use the galaxy nexus toolkit to unlock bootloader, root
Apparently the power outage messed up your partitions, causing the unlock command to fail. And since your bootloader is still locked, both fastboot and Odin cannot be used to flash anything. If you have root, you can try unlocking the bootloader with the bootunlocker app.
PS: advice that says 'use toolkit X' is pointless by the way. Toolkits are just GUIs around fastboot and adb, if the raw fastboot commands don't work, Toolkits won't work either.
Petrovski80 said:
Apparently the power outage messed up your partitions, causing the unlock command to fail. And since your bootloader is still locked, both fastboot and Odin cannot be used to flash anything. If you have root, you can try unlocking the bootloader with the bootunlocker app.
PS: advice that says 'use toolkit X' is pointless by the way. Toolkits are just GUIs around fastboot and adb, if the raw fastboot commands don't work, Toolkits won't work either.
Click to expand...
Click to collapse
Thats true, every tool kit i have tried has failed, even fastboot commands, at least the latter tell you that it fails. Where can i download the bootunlocker app? Does my Nexus 7 have to boot into the rom to do this? Because mine can't. :S
Petrovski80 said:
Apparently the power outage messed up your partitions, causing the unlock command to fail. And since your bootloader is still locked, both fastboot and Odin cannot be used to flash anything. If you have root, you can try unlocking the bootloader with the bootunlocker app.
PS: advice that says 'use toolkit X' is pointless by the way. Toolkits are just GUIs around fastboot and adb, if the raw fastboot commands don't work, Toolkits won't work either.
Click to expand...
Click to collapse
Incorrect.
Signed images will flash correctly with a locked bootloader.
Jubakuba said:
Incorrect.
Signed images will flash correctly with a locked bootloader.
Click to expand...
Click to collapse
Would you be kind to help me with the instructions and the signed image for nexus 7 needed to be flashed over a locked bootloader? I would greatly appreciate it
AndiS21 said:
Would you be kind to help me with the instructions and the signed image for nexus 7 needed to be flashed over a locked bootloader? I would greatly appreciate it
Click to expand...
Click to collapse
Ask Google or Samsung, they have the keys to sign it. Also, this is the galaxy nexus forums.
Sent from my i9250
OP, OMAP flash?

Your device is corrupt. It can't be trusted and will not boot

Hi friends
Please give me suggestion or guide how to solve problem about handset booting after mistakenly handset OEM locked through fastboot
It enter to fastboot mode but not going to recovery mode or restart in system mode
Is there any solution
If yes then please help me
fastboot oem unlock ?
Actually ive unlocked OEM and install twrp recovery and installed freedom os
Then while checking OEM status ive enter command fastboot OEM lock
It ask me I've pressed yes after that the massage is came after restart as your device is corrupt it can't be trusted and will not boot
After that it enter to fastboot but not going to recovery mode or system
While type command in fastboot OEM unlock massege come failed
This happens because your bootloader has been unlocked at one time. There is no going back, even if you use "fastboot oem lock" later.
Edit: Just noticed the part about your device will not boot. You need to find the system image and flash it. I read somewhere today that OnePlus just released the system image for 4.7.4.
Can you unlock again?
@op, IMHO the best possible solution will be to flash stock rom image and stock recovery if required but I think when you flash stock image it will also flash stock recovery.
When you turn off the phone and boot it with VOLUME UP plus POWER, this should send you straight away to Fastboot. Try if you can unlock again, otherwise... bad luck - you'll need a restore session with 1+.
the Doctor said:
This happens because your bootloader has been unlocked at one time. There is no going back, even if you use "fastboot oem lock" later.
Click to expand...
Click to collapse
Not to be unrespectful, but you're wrong, it is absolutely possible to relock bootloader without problems.
IMHO, trouble happened because he had a custom rom onboard... and a locked bootloader does exactly its purpose... to not boot insecure firmware!
jonsat said:
Not to be unrespectful, but you're wrong, it is absolutely possible to relock bootloader without problems.
IMHO, trouble happened because he had a custom rom onboard... and a locked bootloader does exactly its purpose... to not boot insecure firmware!
Click to expand...
Click to collapse
After looking into it further, I agree with you. That's what I get for having a bootloader-locked Samsung device for two years. I must be getting rusty!
Yes, the bootloader can be re-locked. There may still be a tamper flag as with previous OnePlus devices. But having a locked bootloader with non-OEM software would likely cause the problem he is describing. So, he needs to flash the factory image from bootloader.
I've requested to 1+support for restore remote session
Support send me file link and l2 will assist me in within 2 days
DO NOT RELOCK BOOTLOADER UNLESS U READ UP FIRST!!!!!, its worth just waiting the few seconds after reboot, then to go and try to relock the bootloader
I've restored oneplus 5t through remote session
it become as company new mobile
After that OEM also unlock
Thanks oneplus supports.
kaihansen2001 said:
Can you unlock again?
Click to expand...
Click to collapse
Yes ive unlock Bootloader
Rdxsammm said:
I've restored oneplus 5t through remote session
it become as company new mobile
After that OEM also unlock
Thanks oneplus supports.
Click to expand...
Click to collapse
How did you do it? can you guide me too?
sam razzy said:
How did you do it? can you guide me too?
Click to expand...
Click to collapse
Have you dumpling files and MSM download tools for oneplus 5t
If you have then restore op5t after success it work as new mobile.
But you can get basic dumpling file from oneplus support remote session.
You have to create ticket and chat with oneplus support
oneplus 5 device corrupt and it cant be trusted and will not bootr
hrushi0130 said:
oneplus 5 device corrupt and it cant be trusted and will not bootr
Click to expand...
Click to collapse
Did you by any chance re-lock the bootloader with a custom recovery and custom ROM flashed?
It's because of custom recovery.
Just flash stock recovery image before locking the bootloader.
This fixed for me.
Rdxsammm said:
Actually ive unlocked OEM and install twrp recovery and installed freedom os
Then while checking OEM status ive enter command fastboot OEM lock
It ask me I've pressed yes after that the massage is came after restart as your device is corrupt it can't be trusted and will not boot
After that it enter to fastboot but not going to recovery mode or system
While type command in fastboot OEM unlock massege come failed
Click to expand...
Click to collapse
You unlocked bootloader, flashed rom (custom) and relocked bootloader? Never lock your bootloader on a custom rom! Just enter fastboot again flash twrp (manual/force reboot recovery), copy internal storage to pc then wipe/format everything. Format data. Factory reset then flash latest official rom and reboot

Pixel XL Android P DP4 soft brick

Hi,
Like the title says, my Pixel XL is bootlooping.
The only thing that works is getting to bootloader, I can't even get to recovery without it booting again. The biggest problem is that it's OEM locked and obviously I can't unlock it via developer options.
Is there any way to unlock it without booting to the OS?
Don't Ask said:
Hi,
Like the title says, my Pixel XL is bootlooping.
The only thing that works is getting to bootloader, I can't even get to recovery without it booting again. The biggest problem is that it's OEM locked and obviously I can't unlock it via developer options.
Is there any way to unlock it without booting to the OS?
Click to expand...
Click to collapse
OEM unlock must be toggled before unlocking bootloader or CMD won't work, Can't you flash stock OTA in the recovery? https://developers.google.com/android/ota You can sideload the zip and should flash it to save your device once you get into the OS unlock your bootloader and avoid a situation like this again
liam_davenport said:
OEM unlock must be toggled before unlocking bootloader or CMD won't work, Can't you flash stock OTA in the recovery? https://developers.google.com/android/ota You can sideload the zip and should flash it to save your device once you get into the OS unlock your bootloader and avoid a situation like this again
Click to expand...
Click to collapse
Thanks, but like I said - I can't get into recovery mode and the phone is OEM locked.
Don't Ask said:
Thanks, but like I said - I can't get into recovery mode and the phone is OEM locked.
Click to expand...
Click to collapse
Sorry missread... My bad Contact Google sounds like an RMA job for this one
Hey, if you can get into the bootloader, there's a high chance you can use fastboot. Using a computer to install adb/fastboot and then using the command line to run
`fastboot reboot recovery` (without the ticks)
Worth a shot, but if you can't get into recovery, I'm afraid the recovery might be failing as well.
khoanguyen96 said:
Hey, if you can get into the bootloader, there's a high chance you can use fastboot. Using a computer to install adb/fastboot and then using the command line to run
`fastboot reboot recovery` (without the ticks)
Worth a shot, but if you can't get into recovery, I'm afraid the recovery might be failing as well.
Click to expand...
Click to collapse
I've tried that as well with no success, it simply starts boot looping again.
I read somewhere about EDL mode, does something that like actually work for the Pixel?
Don't Ask said:
I've tried that as well with no success, it simply starts boot looping again.
I read somewhere about EDL mode, does something that like actually work for the Pixel?
Click to expand...
Click to collapse
Hey, yeah I looked into EDL mode. No luck unfortunately, looks like it requires special files manufacturers only have access to. Is there any way you can do a RMA?

sofrbrick/bootloop

Hi all,
I am new to this forum, but have some experience with rooting and custom roms(oneplus one and samsung)
Now with the Mi Max 3, which was unlocked, i have flashed the recovery twrp-3.2.3-0-nitrogen.img, but I did not realize that
i had to reboot into this recovery from the fastboot mode.
so I endet up with a locked bootloader and bottloop and am not able to unlock the bootloader again.
I think my only solution is the test-point method and a EDL authorized account.
Some help would be greatly appreciated.
thanks
Henry
You don't have to boot into the bootloader from fastboot mode, you can press the power button and volume up button like on almost all other Android phones to boot into TWRP recovery. Sometimes it takes a few attempts to get right, but you should learn how to do it eventually.
Unfortunately it sounds like you had one of the dodgy re-sold Chinese models that had been re-flashed with Global firmware and it's locked your bootloader again on reboot.
Your only option is to use the official Miui Flash tool to boot into fastboot mode, flash the latest Global Developer ROM, and then sign in with your account and apply to unlock the bootloader again using the Miui unlock program. It may be instant but, they'll probably make you wait 720 hours, as the entire point of the program was to stop phones like yours being re-sold outside China.
At least you'll have a usable, non-bricked device though.
Thanks for your answer.
now I have opened the backcover (yes was much work ( I succeded without destroying something) and could apply the test point method to get into the lde mode.
Win10 shows it as qualcomxx at com 3
what is the best way now to awake it to life again? even without unlocking.
hi,
with the test point method I could flash the chinese rom, and the mi max 3 is awaken to life again!
The bootloader is still locked.
I have applied for unlocking, but have to wait some 15 days.
One tip: if the case is open, one can apply a little bit of silicon grease to the small pins on the side of the plastic frame
before closing it. Opening it again is much easier then.
One question: if I replace the recovery.img of the chinese rom with a TWRP image (renamed to recovery.img)
and flash that modified rom with the test point method, could this probaly work?
With a working TWRP one could install other roms without unlocking bootloader.
If yes, which TWRP would you apply?
Thanks
freedoc said:
Hi all,
I am new to this forum, but have some experience with rooting and custom roms(oneplus one and samsung)
Now with the Mi Max 3, which was unlocked, i have flashed the recovery twrp-3.2.3-0-nitrogen.img, but I did not realize that
i had to reboot into this recovery from the fastboot mode.
so I endet up with a locked bootloader and bottloop and am not able to unlock the bootloader again.
I think my only solution is the test-point method and a EDL authorized account.
Some help would be greatly appreciated.
thanks
Henry
Click to expand...
Click to collapse
Flashing a recovery should not lock your bootloader, so I don't know how you did it. Note, that if you are using Xiaomi's firmware tool, you should not forget about unticking the box to lock the bootloader. But I would suggest to stay away from that tool and go command line instead with fastboot.
If you can access fastboot, I'd recommend to flash an official fastboot tgz ROM of your choice. Official ROM should boot even with an unlocked bootloader and you may start all over again more carefully.
So I think you might be able to avoid using EDL mode at this stage.
probally I forgot to untick that box. The bootloader is locked and I have to wait 319 hours.
I have got to love the test point EDL method which is simple and effective, and gave me control over the device again.
If I flash again the chinese fastboot rom (in which I have changed the original recovery.img into TWRP.img, named recovery.img) via the EDL
will that give me an installt TWRP (still with locked bootloader, but possible to install custom roms) or will i have a brick again?
thanks
freedoc said:
probally I forgot to untick that box. The bootloader is locked and I have to wait 319 hours.
I have got to love the test point EDL method which is simple and effective, and gave me control over the device again.
If I flash again the chinese fastboot rom (in which I have changed the original recovery.img into TWRP.img, named recovery.img) via the EDL
will that give me an installt TWRP (still with locked bootloader, but possible to install custom roms) or will i have a brick again?
thanks
Click to expand...
Click to collapse
Only you can answer that question by trying it out. Are you sure you have to wait for the unlocking again? Double check that! As I know you also need a priviliged xiaomi account to be able to resurrect a device in EDL mode.

OEM Locked, and Device is corrupt. Unfixable?

So, long story short I recently decided to try and root my oneplus7t I unfortunately made some mistakes and somehow corrupted some files. I read elsewhere in the forum that I could download the stock rom which I did and then use flash-all and that would allow me to go back to the factory settings so I could lock the oem and just go back to normal because I was tired of the headache. Unfortunately, after using flash-all I locked the oem thinking everything should be stock and it would work properly. But it says device is corrupt and trying to unlock the oem says oem unlocking is disabled.
So did I just completely brick my phone? I don't know of anyway to fix it at this point :/.
kschmitz4 said:
So, long story short I recently decided to try and root my oneplus7t I unfortunately made some mistakes and somehow corrupted some files. I read elsewhere in the forum that I could download the stock rom which I did and then use flash-all and that would allow me to go back to the factory settings so I could lock the oem and just go back to normal because I was tired of the headache. Unfortunately, after using flash-all I locked the oem thinking everything should be stock and it would work properly. But it says device is corrupt and trying to unlock the oem says oem unlocking is disabled.
So did I just completely brick my phone? I don't know of anyway to fix it at this point :/.
Click to expand...
Click to collapse
Can you still boot into bootloader via the hardware keys, whatever that combo is on the 7t?
Boot to bootloader or recovery and factory reset it or so.
Josh McGrath said:
Can you still boot into bootloader via the hardware keys, whatever that combo is on the 7t?
Boot to bootloader or recovery and factory reset it or so.
Click to expand...
Click to collapse
I can get to the bootloader but it's Device State -locked and when I tell it to boot into recovery it says the device is corrupt. When I use fastboot to oem unlock it says I cannot, and I can't flash when oem is locked either.
kschmitz4 said:
I can get to the bootloader but it's Device State -locked and when I tell it to boot into recovery it says the device is corrupt. When I use fastboot to oem unlock it says I cannot, and I can't flash when oem is locked either.
Click to expand...
Click to collapse
Try
fastboot erase userdata and
Fastboot erase cache
Let me know if that works or not we will move on. Probably won't work since it's bootloader locked
You may have to contact OP and while you're at it, get the MSM tool for us all :good:
It says erase is not allowed in locked state . I think this is probably all she wrote for this one. I think I'm just going to send it back tbh, the whole reason I was trying to root it was because it didn't work with Sprint like they said it would. and I was wondering if I could find a way too make it work with custom software. Thanks for trying
Are you able to flash one of these Fastboot ROMs?
Maybe Sideload can work!
https://support.oneplus.com/app/answers/detail/a_id/4583/kw/7t here is official stock file.
https://forums.oneplus.com/threads/how-to-do-flash-through-adb-sideload.509377/
https://www.the***********.com/sideload-ota-update-stock-recovery-adb/
Please refer above links for your knowledge purpose maybe it can help.....
I unfortunately no longer have Twrp installed as I did a flash-all with a stock rom already . If I try and flash recovery it says "flashing is not alllowed in lock state". Sideloading wasn't functional back when I had twrp either as the functionality for it is still in progress. I'll probably try contacting support one more time and see if I can get a T2 who can unbrick it, otherwise I'm just going to send it back. Thanks for the attempts guys!
Edit: As to the flashboot roms I flash-all'ed one of them and that's how I got into this mess :/.
kschmitz4 said:
I unfortunately no longer have Twrp installed as I did a flash-all with a stock rom already . If I try and flash recovery it says "flashing is not alllowed in lock state". Sideloading wasn't functional back when I had twrp either as the functionality for it is still in progress. I'll probably try contacting support one more time and see if I can get a T2 who can unbrick it, otherwise I'm just going to send it back. Thanks for the attempts guys!
Edit: As to the flashboot roms I flash-all'ed one of them and that's how I got into this mess :/.
Click to expand...
Click to collapse
I ended up needing to flash the fastboot 10.0.3 firmware and was able to do a local upgrade to 10.0.4 that way, then flashing a patched boot.img via fastboot
I can't run any flash commands as my oem is locked. I don't suppose there's anyway around that?
kschmitz4 said:
I can't run any flash commands as my oem is locked. I don't suppose there's anyway around that?
Click to expand...
Click to collapse
How did you flash twrp with it oem locked??That doesnt make sense
I had twrp on it when the oem was unlocked, I was trying to reset the device to stock, so I did a flash-all and then oem locked it. But for some reason the repair was unsuccessful, and now it says my device is corrupted and I forgot to turn on oem unlocking in the settings on my phone after the flash-all before I did the oem-lock.
kschmitz4 said:
I had twrp on it when the oem was unlocked, I was trying to reset the device to stock, so I did a flash-all and then oem locked it. But for some reason the repair was unsuccessful, and now it says my device is corrupted and I forgot to turn on oem unlocking in the settings on my phone after the flash-all before I did the oem-lock.
Click to expand...
Click to collapse
You should have no issues reflashing the stock images
I cannot flash anything. Because my OEM state is locked.
Boot to Stock Recovery ?
Holding for a long time Volume Down + Power Buttons while booting your phone ?
Volume down plus power button takes me to "Your device is corrupt and will not boot"
kschmitz4 said:
Volume down plus power button takes me to "Your device is corrupt and will not boot"
Click to expand...
Click to collapse
Looks like you will need the MSM tool to fix this issue. You'll have to contact OP support and they will remote in your PC, load their software and flash it 100pct back to stock.
Also, disconnect them before they can delete the MSM tool so we can have it here in the community
kschmitz4 said:
Volume down plus power button takes me to "Your device is corrupt and will not boot"
Click to expand...
Click to collapse
Press volume up/down and power, reboot to fastboot. Unlock bootloader again. Install update from settings, reboot and install it again. (local install)
Factory reset in setting, reboot fastboot, lock bootloader. Reboot and untick unlock bootloader in developer settings.
Don't know if it's too late but I believe there's a working MSM tool now

Categories

Resources