Alldocube - T1026 (kPad) Bootloader Unlocking - Upgrading, Modifying and Unlocking

Surprised that I haven't come across too much regarding this tablet. It's relatively cheap, but has a wonderful screen, with cel data and SD card support. And not a bad resolution. (Not 4K, but ALMOST 2k...) This device seems to be running a SpreadTrun / SPD system under the hood.
Having issues getting it rooted and bootloader unlocked.
First, Rooting via boot.img and Magisk -
I am able to get the boot.img file and have Magisk patch it fine. However, when I go to re-write the boot.img file, fastboot gives me the following:
C:\>fastboot flash boot_a magisk_patched-22100_2U5Ga.img
Warning: skip copying boot_a image avb footer (boot_a partition size: 0, boot_a image size: 67108864).
Sending 'boot_a' (65536 KB) OKAY [ 2.422s]
Writing 'boot_a' FAILED (remote: 'Flashing Lock Flag is locked. Please unlock it first!')
fastboot: error: Command failed
SPD's UpgradeFlash won't let me select JUST to flash the boot file - it forces everything to be flashed, which resets the device. Because of that, when I insert the patched boot.img in, it causes the tablet to bootloop.
Trying to unlock bootloader -
Reading through different methods for SPD devices, I'm running into deadends. With both ADB Debug and OEM Unlock enabled, running the following commands don't work:
C:\>fastboot flashing unlock
FAILED (remote: 'unknown cmd.')
C:\>fastboot oem unlock
FAILED (remote: 'Unlock bootloader fail.')
I thought that perhaps the method of flashing the signature (signature.pim file) was needed. However, following that attempt, the command yields:
C:\>fastboot flashing unlock signature.bin
fastboot: usage: unknown 'flashing' command unlock
(Same error is given for 'unlock_critical' and 'unlock_bootloader'.)
Anyone know of an alternate way to flash JUST the boot.img files to an SPD device?

Quick bump!
One interesting thing I have noticed - every time after I run the second command ('oen unlock'), any command sent AFTER that will hang. As if the tablet's expecting something else.

Any luck? I've also got this tablet, seems like unisoc have different bootloader unlock procedure, read that it needs linux with custom adb tools

I actually unlocked the bootloader on mine several months ago. Details aren't fresh in my mind but I do remember a few things that may help you.
1) You absolutely need the signature file. I got mine by installing an app "spreatrum tools" on the tablet.
2) It only works with a specific version of fastboot.
3) According to my terminal history, the command to unlock could be "fastboot.exe flashing unlock_bootloader signature.bin" or the one posted by OP: "fastboot flashing unlock signature.bin". At least one of these works but I don't remember which since I used them both.
Pretty sure I got both the working version of fastboot (windows version, not linux) and the app here on the forum. Whoever posted those files originally deserves the credits but, again, I don't remember who or where so... Luckily I still have both files on my NAS so I'm attaching them.
Anyway, there, have fun.

So this can also work, nice!

troolie said:
I actually unlocked the bootloader on mine several months ago. Details aren't fresh in my mind but I do remember a few things that may help you.
Anyway, there, have fun.
Click to expand...
Click to collapse
Thanks so much, already unlocked my BL (through modified adb via Linux) but can't proceed to root it, have you rooted yours?

Nope. My plan was to unlock in order to install a custom recovery as I thought there's a good chance the one for iplay40 might work. Turns out I ended up with a brick so I went back to stock.
My immediate concern was to get rid of system apps but adb shell works well enough for that so...
Actually, I'm more interested in running generic GSI if at all possible, considering alldocube is unlikely to ever update the stock rom.

troolie said:
I actually unlocked the bootloader on mine several months ago. Details aren't fresh in my mind but I do remember a few things that may help you.
Click to expand...
Click to collapse
Vvtaewoo12 said:
Any luck? I've also got this tablet, seems like unisoc have different bootloader unlock procedure, read that it needs linux with custom adb tools
Click to expand...
Click to collapse
Sorry for the silence guys, had a death in the family that took me away from playing with this tablet for a while.
Glad you both got it - I actually was able to get in touch with someone AT AlldoCube, and they replied saying that the bootloader IS UNLOCKED in the same fashion that the iPlay40 is. (Which isn't too much of a surprise - the back cover of my kPad actually has the iPlay 40 model number on it. Heh.) I followed the instructions in the iPlay 40 thread exactly (including the one command that's run that the output seems to not be used), and it worked.
Like you both, though, I haven't been able to root - Because of the family issues, I haven't tried in a while, but I remember getting as far as trying to flash a modified Magisk boot.img - at which point, the tablet goes into bootloop. I blieve that we need a signed vbmeta file, though I have no idea yet how to generate/flash that.
I have NOT tried the iPlay40 rooting instructions in one post, and I'm admittedly not even sure that I'm using the Spedtrum flashing applications correctly.

Help me unlock bootloader ipay 40
U have trailer video URL/??

U use Ubuntu linux but do not!!

Taoismixi said:
U use Ubuntu linux but do not!!
Click to expand...
Click to collapse
Wrong thread. This is not about the iPlay 40.

Related

[A]"Root"/Unlock/Hboot 2.18/Gingerbread 2.3.5/ROM Flashing

Okay, so I recently got an HTC EVO for a sibling. It has the latest software on it and of course, can't root it!
Here's what I did to accomplish "root", unlock actually, can still flash ROMs.
I have an EVO 3D with dreaded Hboot 1.50. That can be "rooted", I thought, and proceeded to do the same steps with the EVO and the HTCDEV website for unlocking the bootloader.
Any who, I found that the easiest way is to start off with what's available.
Download the HTC Super Tool, it contains a very important folder (root) which contains necessary files. The tool comes in form of a .rar file, extract the contents into its own folder. Once extracted, you should see that root folder. This folder is from where you're going to run your fastboot commands, instructions to come.
http://forum.xda-developers.com/showpost.php?p=19277775&postcount=1
Go to http://www.htcdev.com/bootloader/ (you'll have to register), off to the right of the page is a drop-down menu, select the last option. There's an option for EVO 4G(Korea), but it's not for us. Follow the instructions on the page, with the exception of the SDK folder and Java runtime download/steps, this is where the root folder from the HTC Super Tool comes into play. Step 5 makes mention to needing 3 files in particular, these are in that root folder, go to step 6. Step 10 can seem like a big task, but it's not that bad. You'll get an email, follow what the email says. Your phone will now be unlocked with S-ON. At this point, you're able to flash a ROM, but must have a custom recovery to do so. The issue is with S-ON, you can not flash a ROM with custom kernel by default, you have to push the boot.img(which includes the kernel)/kernel via fastboot in command prompt.
You can download your preferred recovery image and load onto the phone via fastboot. Download your recovery image and place it in that root folder you have from the SuperTool. Now open a command window addressed to the mentioned folder: i.e., (here's where mine is) C:\Users\Isidro\Desktop\HTC SuperTool\root, so point the prompt to "cd C:\Users\Isidro\Desktop\HTC SuperTool\root"(without quotes) or wherever you have that folder. Now, at the prompt type "fastboot flash recovery recovery.img{doing this puts your recovery on permanently, booting into recovery allows for flashing custom ROMs and kernels simultaneously}"[no quotes (replace "recovery" with your appropriate file's name, unless you rename it recovery)] example = fastboot flash recovery recovery-twrp-supersonic-1.1.1.img. I use TWRP, personally.
http://teamw.in/project/twrp/3
Okay, so you have your custom recovery on the phone. It will only boot the recovery however, when told to do so via command prompt. Unless, you invest in Flash Image GUI by joeykrim, it will flash the recovery so that you have access even without a computer.Updated a previous step and Flash Image GUI is not really needed, other than if you want to flash to different kernels/recoveries on-the-fly.
https://market.android.com/details?...wyLDEsImNvbS5qb2V5a3JpbS5mbGFzaGltYWdlZ3VpIl0.
Anyway, now that you have your custom recovery put your preferred ROM's zip on the root of your SD card. Hopefully, the recovery of your choosing has USB storage mounting capabilities to move the file over. You'll also have to extract the zip of your ROM into it's own folder on your computer, you'll see a boot.img file, copy this also into your root folder.
Now, all the chips are in place. In your recovery reboot the phone into bootloader so that you can get to fastboot and you see fastboot usb on the screen.
Your command prompt should still be up, if not reopen it and point to appropriate folder. Type "fastboot flash boot.img" (no quotes), this flashes your ROM's kernel. Type "fastboot boot recovery.img" (no quotes). Now install your ROM zip in the recovery you just booted into. <This step not needed if you boot into recovery via fastboot and flash your ROM's zip, while still connected
Below are how the steps are in numerical order, tried to make it make sense for all parties involved.
1) Download HTC SuperTool, extract into its own folder. Root folder in here.
2) Download your preferred custom recovery, place in root folder from SuperTool zip.
3)Use HTCDEV method for unlocking: skip step 5; adb.exe, adbwinapi.dll and fastboot.exe found in root folder from SuperTool.
4)Reboot into fastboot. Your command prompt should still be open.
5) Flash your recovery onto the phone permanently via fastboot. "fastboot flash recovery recovery.img"(recovery.img=your recovery's name)
6)Power down your phone in your recovery, boot into bootloader and choose fastboot. Boot recovery via command prompt, type "fastboot boot recovery.img" where recovery is the name of your custom recovery image.
7)Mount your phone and copy the ROM zip onto the SD card root. Do this in your recovery.
8) Flash your ROM zip.
Congrats, your ROMed and unlocked. Not a true root, but you have access to flashing. I myself haven't figured out how to flash a custom kernel, without the help of flash image gui by joeykrim. Use joeykrim's app, when wanting to try custom kernels on the fly But, you can always flash whatever kernel the ROM has by extracting the rom and moving the boot.img file into the root folder, remember to remove the old boot.img file out of the root folder first.
Okay so flashing a custom kernel is done via recovery, when it is booted via fastboot. You can also flash the full ROM, kernel and all in the same manner, when recovery is booted via fastboot command. Finally got this myself after reading joeykrim's explanation, again.
http://forum.xda-developers.com/showpost.php?p=18594963&postcount=31
If you check out the 1st post for HBOOT 1.5 users(should work for HBOOT 2.18), you can flash kernel from the app followed by rebooting into recovery and flashing the ROM. All from the comfort of your phone sans fastboot. Once, of course, you've flashed a recovery onto the phone.
http://forum.xda-developers.com/showthread.php?t=1453617
How to flash a ROM via fastboot, for those that are bootloader "unlocked" via HTCDEV method. joeykrim does mention that you can flash the kernel via his app also followed by flashing/installing the ROM via the recovery.
Wow, I know it was long winded! But, it is possible. I will try to post a few pics and maybe do a video.
Thanks to all the great devs, contributors and testers alike.
Video links, finally! It's 2 parts the DEV unlocking and the actual flashing.
Unlocking: http://youtu.be/TSiMiaNMTjU
Recovery/ROM Flashing(had to make it a 2 part): Part1: http://youtu.be/bz8KgtZByFI
Part2: http://youtu.be/nZEGu0j_BEk
As always, you do this at your own risk. I am only making mention as to how I was able to accomplish loading a ROM onto a phone with the new HBOOT 2.18.
+1 if this works and I'm pretty sure it do.
Read this over in the Evo 3D forum. I don't trust apps to flash .img so this is what I would do.
Adb: (phone must be plugged into computer)
adb reboot bootloader
fastboot boot recovery.img
This would boot you into recovery with the ability to flash to the boot partition (kernels and ROMs with custom kernels)
Be back, gotta make sure commands are correct
Edit: commands are correct. Found it by JTNiggle, kudos to him
Sent from my PC36100 using xda premium
Just for clarity here... (i've rooted my phone in the past, but accidentally accepted the OTA update yesterday after finding a mislabled youtube video which lead me to believe there was already a method for rooting/flashing) this method will unlock the phone and allow flashing, but not allow things that require root, such as wifi tether and overclocking. Is that correct?
shorty6049 said:
Just for clarity here... (i've rooted my phone in the past, but accidentally accepted the OTA update yesterday after finding a mislabled youtube video which lead me to believe there was already a method for rooting/flashing) this method will unlock the phone and allow flashing, but not allow things that require root, such as wifi tether and overclocking. Is that correct?
Click to expand...
Click to collapse
The only things you cant do is flash splash screens. Everything else will work but you have to do it differently
Sent from my PC36100 using XDA App
shorty6049 said:
Just for clarity here... (i've rooted my phone in the past, but accidentally accepted the OTA update yesterday after finding a mislabled youtube video which lead me to believe there was already a method for rooting/flashing) this method will unlock the phone and allow flashing, but not allow things that require root, such as wifi tether and overclocking. Is that correct?
Click to expand...
Click to collapse
Did you use unrevoked or Revolutionary before? If you used unrevoked, then you might want to go check your Hboot to make sure you are S-Off. If you used Revolutionary and you accepted the OTA, then you don't have S-Off.
S-Off allows you to write custom software to all of your phone's memory partitions (ROMs, custom kernels, splash screens, radios, recoveries). It does not allow you to use Wi-Fi Tether by itself, you would need Superuser privileges ("rooting").
This method "unlocks" your bootloader. It is much more restrictive with what you can do than S-Off. You cannot flash custom kernels, radios, recoveries, and ROMs with custom kernels in a normal way.
You would need to use this method to "unlock" your bootloader. Then you would need to flash a recovery over ADB. Then you would need to flash Superuser in order to Wi-Fi Tether. Overclocking, you would need a custom kernel for that. You would have to boot into recovery using something called "Fastboot" in order to do that
tropicalbrit said:
Did you use unrevoked or Revolutionary before? If you used unrevoked, then you might want to go check your Hboot to make sure you are S-Off. If you used Revolutionary and you accepted the OTA, then you don't have S-Off.
S-Off allows you to write custom software to all of your phone's memory partitions (ROMs, custom kernels, splash screens, radios, recoveries). It does not allow you to use Wi-Fi Tether by itself, you would need Superuser privileges ("rooting").
This method "unlocks" your bootloader. It is much more restrictive with what you can do than S-Off. You cannot flash custom kernels, radios, recoveries, and ROMs with custom kernels in a normal way.
You would need to use this method to "unlock" your bootloader. Then you would need to flash a recovery over ADB. Then you would need to flash Superuser in order to Wi-Fi Tether. Overclocking, you would need a custom kernel for that. You would have to boot into recovery using something called "Fastboot" in order to do that
Click to expand...
Click to collapse
I apologize , I tried editing my original post but got an error saying i had to wait 25 minutes or something, so I went and took a shower instead. Currently my phone is completely unrooted and locked. Its a brand new phone that sprint gave me yesterday becuase of some issues with my old one.
I'd like to do this right though, and I'm not quite sure how comfortable I am with the method being presented here since i guess I dont fully understand all the implications of doing it like this, vs. waiting it out and doing it how I usually would (which in the past has been unrevoked and revolutionary) .
I guess my biggest fear as of right now is that I'd do it this way, then in a week or two, revolutionary will update to include hboot 2.18 and I wont know what to do to get rooted again or something... (I generally learn as much as I need to know in order to get stuff done or fixed since I'm not a programmer or anything )
tropicalbrit said:
Read this over in the Evo 3D forum. I don't trust apps to flash .img so this is what I would do.
Adb: (phone must be plugged into computer)
adb reboot bootloader
fastboot boot recovery.img
This would boot you into recovery with the ability to flash to the boot partition (kernels and ROMs with custom kernels)
Be back, gotta make sure commands are correct
Edit: commands are correct. Found it by JTNiggle, kudos to him
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
This is how joeykrim explains about the boot partition with S-On, HTCDEV unlock method.
http://forum.xda-developers.com/showpost.php?p=18594963&postcount=31
shorty6049 said:
I apologize , I tried editing my original post but got an error saying i had to wait 25 minutes or something, so I went and took a shower instead. Currently my phone is completely unrooted and locked. Its a brand new phone that sprint gave me yesterday becuase of some issues with my old one.
I'd like to do this right though, and I'm not quite sure how comfortable I am with the method being presented here since i guess I dont fully understand all the implications of doing it like this, vs. waiting it out and doing it how I usually would (which in the past has been unrevoked and revolutionary) .
I guess my biggest fear as of right now is that I'd do it this way, then in a week or two, revolutionary will update to include hboot 2.18 and I wont know what to do to get rooted again or something... (I generally learn as much as I need to know in order to get stuff done or fixed since I'm not a programmer or anything )
Click to expand...
Click to collapse
In the EVO 3D development forums, full on S-Off stopped being worked on because people were able to accomplish ROM flashing and kernel flashing via HTCDEV unlocked bootloaders, S-On and adb fastboot via command prompt and joeykrim's flash image gui app. I hope it doesn't happen to you guys here, but it may. Someone, somewhere may be working on it, is my hope. Having S-Off, makes life oh so simple. There shouldn't be any ramifications to unlocking the bootloader utilizing HTCDEV method and at if at some point S-Off were accomplished you would have on less thing to do for root.
intrlude said:
In the EVO 3D development forums, full on S-Off stopped being worked on because people were able to accomplish ROM flashing and kernel flashing via HTCDEV unlocked bootloaders, S-On and adb fastboot via command prompt and joeykrim's flash image gui app. I hope it doesn't happen to you guys here, but it may. Someone, somewhere may be working on it, is my hope. Having S-Off, makes life oh so simple. There shouldn't be any ramifications to unlocking the bootloader utilizing HTCDEV method and at if at some point S-Off were accomplished you would have on less thing to do for root.
Click to expand...
Click to collapse
I guess I still don't fully understand all of this (its been kind of a long day) and what the actual differences are between this, and what i'd get when using , just for example becuase its the method I remember most clearly, unrevoked. I rooted and flashed ICS to my xoom a couple weeks ago using a method that's probably similar to the one you're detailing here (in that I had to push it through adb) but I'm still a bit worried that i'll end up getting in over my head with all the different techniques.
I'm kind of assuming flashing roms through ROM manager wouldn't be an option anymore? I don't want to inconvenience anyone here with a bunch of stupid questions though, so I'll try figuring it out on my own, but if anyone feels compelled , they can certainly help out. It was just so simple rooting with unrevoked and revolutionary....
shorty6049 said:
I guess I still don't fully understand all of this (its been kind of a long day) and what the actual differences are between this, and what i'd get when using , just for example becuase its the method I remember most clearly, unrevoked. I rooted and flashed ICS to my xoom a couple weeks ago using a method that's probably similar to the one you're detailing here (in that I had to push it through adb) but I'm still a bit worried that i'll end up getting in over my head with all the different techniques.
I'm kind of assuming flashing roms through ROM manager wouldn't be an option anymore? I don't want to inconvenience anyone here with a bunch of stupid questions though, so I'll try figuring it out on my own, but if anyone feels compelled , they can certainly help out. It was just so simple rooting with unrevoked and revolutionary....
Click to expand...
Click to collapse
If the phone in question has the latest update on it which brings with it 2.3.5 and HBOOT-2.18, then ROM manager would not be an option. I am hopeful that revolutionary.io will be updated. But, if it comes to pass that S-OFF can no longer be accomplished, much like the fate of HBOOT-1.50 3D users. HTCDEV bootloader unlocking and flashing boot.img and booting into a recovery.img via fastboot will be the only answer.
alright , ONE last question for now...
IS there a method of reverting back to a previous firmware version (2.3.3 with hboot 2.15 for example) or is that not possible?
I know i've seen that mentioned in previous OTA update threads, but (as expected this soon after an update) haven't seen anything regarding this one yet.
i'm not in any huge hurry to do all of this, so I can wait a bit to see if revolutionary will figure it out, although once CM9 alpha is released I'll probably end up doing something. Thanks for your help on this, by the way, I appreciate your patience with me
CAUTION: Follow the steps exactly. If you type something in incorrectly -- it can screw something up.
Hopefully someone can help me get this sorted out:
Near the last step where you are supposed to type "fastboot boot boot recovery.img" in order to reboot into recovery to flash your custom ROM, I accidentally ended up typing "Fastboot flash boot recovery.img" and can no longer either reboot my phone without it going in a bootloop, and get the error "cannot load boot" when attempting to boot the recovery image.
I have tried powering it off, removing the battery, and from there attempting to reboot into fastboot and reflash the boot.img and recovery -- with the same bad results -- copied and pasted the attempts below.
Does anyone have any good advice on what to do?
Code:
C:\htc\root>fastboot flash boot boot.img
sending 'boot' (1976 KB)... OKAY [ 0.649s]
writing 'boot'... OKAY [ 0.773s]
finished. total time: 1.422s
C:\htc\root>fastboot flash boot recovery.img
sending 'boot' (3678 KB)... OKAY [ 1.166s]
writing 'boot'... FAILED (remote: image update error)
finished. total time: 1.166s
C:\htc\root>fastboot boot boot recovery.img
cannot load 'boot'
C:\htc\root>fastboot boot boot recovery.img
cannot load 'boot'
C:\htc\root>fastboot flash boot recovery.img
sending 'boot' (3678 KB)... OKAY [ 1.178s]
writing 'boot'... FAILED (remote: image update error)
finished. total time: 1.183s
C:\htc\root>fastboot boot boot recovery.img
cannot load 'boot'
C:\htc\root>fastboot flash boot boot.img
sending 'boot' (1976 KB)... OKAY [ 0.650s]
writing 'boot'... OKAY [ 0.776s]
finished. total time: 1.426s
C:\htc\root>fastboot boot boot recovery.img
cannot load 'boot'
C:\htc\root>
hilga007 said:
CAUTION: Follow the steps exactly. If you type something in incorrectly -- it can screw something up.
Hopefully someone can help me get this sorted out:
Near the last step where you are supposed to type "fastboot boot boot recovery.img" in order to reboot into recovery to flash your custom ROM, I accidentally ended up typing "Fastboot flash boot recovery.img" and can no longer either reboot my phone without it going in a bootloop, and get the error "cannot load boot" when attempting to boot the recovery image.
I have tried powering it off, removing the battery, and from there attempting to reboot into fastboot and reflash the boot.img and recovery -- with the same bad results -- copied and pasted the attempts below.
Does anyone have any good advice on what to do?
Code:
C:\htc\root>fastboot flash boot boot.img
sending 'boot' (1976 KB)... OKAY [ 0.649s]
writing 'boot'... OKAY [ 0.773s]
finished. total time: 1.422s
C:\htc\root>fastboot flash boot recovery.img
sending 'boot' (3678 KB)... OKAY [ 1.166s]
writing 'boot'... FAILED (remote: image update error)
finished. total time: 1.166s
C:\htc\root>fastboot boot boot recovery.img
cannot load 'boot'
C:\htc\root>fastboot boot boot recovery.img
cannot load 'boot'
C:\htc\root>fastboot flash boot recovery.img
sending 'boot' (3678 KB)... OKAY [ 1.178s]
writing 'boot'... FAILED (remote: image update error)
finished. total time: 1.183s
C:\htc\root>fastboot boot boot recovery.img
cannot load 'boot'
C:\htc\root>fastboot flash boot boot.img
sending 'boot' (1976 KB)... OKAY [ 0.650s]
writing 'boot'... OKAY [ 0.776s]
finished. total time: 1.426s
C:\htc\root>fastboot boot boot recovery.img
cannot load 'boot'
C:\htc\root>
Click to expand...
Click to collapse
When you remove your battery and then proceed to enter the bootloader, it does say *** UNLOCKED ***? Also, your recovery.img file is in that folder, right? If you "fastboot flash boot boot.img" and that went through, then we just have to get you into the recovery.
Make sure that your recovery.img file is in the folder you have the command prompt pointed to and "fastboot boot recovery.img", yes try with just one boot in there. Let us know if you have any luck.
Code:
C:\Users\Isidro>cd C:\Users\Isidro\Desktop\HTC SuperTool\root
C:\Users\Isidro\Desktop\HTC SuperTool\root>fastboot boot boot recovery-twrp-supersonic-1.1.1.img
cannot load 'boot'
C:\Users\Isidro\Desktop\HTC SuperTool\root>fastboot boot recovery-twrp-supersonic-1.1.1.img
downloading 'boot.img'... OKAY [ 1.128s]
booting... OKAY [ 0.002s]
finished. total time: 1.132s
C:\Users\Isidro\Desktop\HTC SuperTool\root>
I have a question. Like a dumb ass, I accepted the newest ota without knowing that it changed my hboot version and to 2.3.5 so using revolutionary is not an option. I can however press the power button and the volume down button to get to the bootloader like anyone else can. Now my question is, the two files used to unroot 2.3.3, the hboot zip and stock non rooted Rom zip, if I place the hboot zip on the root of my SD card and power up into the boot loader and let the phone pick up the pcimg36 file I believe it is, will that brick my phone if I attempt to change the hboot then load the stock, non rooted Rom? Thanks for any help.
AirborneCmH said:
I have a question. Like a dumb ass, I accepted the newest ota without knowing that it changed my hboot version and to 2.3.5 so using revolutionary is not an option. I can however press the power button and the volume down button to get to the bootloader like anyone else can. Now my question is, the two files used to unroot 2.3.3, the hboot zip and stock non rooted Rom zip, if I place the hboot zip on the root of my SD card and power up into the boot loader and let the phone pick up the pcimg36 file I believe it is, will that brick my phone if I attempt to change the hboot then load the stock, non rooted Rom? Thanks for any help.
Click to expand...
Click to collapse
This may happen if you try that.
http://forum.xda-developers.com/showthread.php?p=21702804
Sent from the 3Dimension
intrlude said:
This may happen if you try that.
http://forum.xda-developers.com/showthread.php?p=21702804
Sent from the 3Dimension
Click to expand...
Click to collapse
Your right. That may happen. I'm not messing with the hex editor but it would be messing with the hboot version so I haven't done it because I don't want to turn my EVO into a paper weight, just didn't know if that would be an option. Thanks for the info.
Everything works
Hey Fellas, okay so after ranting and raving on this forum about my jacked up phone.... i did soley make the mistake that many of you have made by updating 2.3.5 with hboot 2.18...well after finding this on the great forum of XDA i spent about a good 4 + hours farting around until i finally got my phone perfect...4G works, i have sinister lv9 rom on my EVO 4G, i have setcpu,i installed the timat kernel, im overclocked to 1.228Ghz, and i have wifi tether all enables + superuser, which was already built into the rom, my phone is no different than it was b4 the update, except it took me 4 hours to get where revolution took me 5 minutes to get to, major thanks!!!
---------- Post added at 05:36 AM ---------- Previous post was at 05:34 AM ----------
Interlude, major thanks..
---------- Post added at 05:38 AM ---------- Previous post was at 05:36 AM ----------
its not "fastboot boot boot recovery.img...the problem i had is putting in "Boot" 2 times...its actually "fastboot boot recovery.img"
Middleasternplayer said:
Hey Fellas, okay so after ranting and raving on this forum about my jacked up phone.... i did soley make the mistake that many of you have made by updating 2.3.5 with hboot 2.18...well after finding this on the great forum of XDA i spent about a good 4 + hours farting around until i finally got my phone perfect...4G works, i have sinister lv9 rom on my EVO 4G, i have setcpu,i installed the timat kernel, im overclocked to 1.228Ghz, and i have wifi tether all enables + superuser, which was already built into the rom, my phone is no different than it was b4 the update, except it took me 4 hours to get where revolution took me 5 minutes to get to, major thanks!!!
---------- Post added at 05:36 AM ---------- Previous post was at 05:34 AM ----------
Interlude, major thanks..
---------- Post added at 05:38 AM ---------- Previous post was at 05:36 AM ----------
its not "fastboot boot boot recovery.img...the problem i had is putting in "Boot" 2 times...its actually "fastboot boot recovery.img"
Click to expand...
Click to collapse
So jealous.... So.. I tend to not stay on one ROM for very long (before I accidentally did this update I had been jumping around to different ICS builds and CM7) would you say that this would be worth the time ? From the sounds of it, even doing something simple like flashing a different ROM , or making a nandroid back up (if it even lets you do that) is a somewhat time-consuming endeavor. What's your thought?
EDIT- Alright, sorry guys. This was way easier than I was expecting. Pretty similar unlocking a Xoom actually. Still not quite sure how to do anything other than flash a Rom, but at least I can have my ICS again...
hey guys,
quick question. i was just wandering if you can do something similar to the evo 3d. with the evo 3d it is possible to go into recovery via fastboot and then just flash a rom and kernel like normal. but you need to have the recovery.img in the tools folder and then have adb boot into bootloader
HTML:
adb reboot bootloader
then
HTML:
fastboot boot recovery.img
after that your phone should boot into recovery and then from there you can flash away like normal.
i'm just wandering if this is possible with the new hboot on the og evo. any help would be greatly appreciated.
thanx

[Q] Unrooted Device Stuck in Bootloop

Hi guys,
My phone (GSM yakjuzs) was stuck in bootloop ages ago. Still can't find a solution to this. It was running 4.0.2, unrooted. At first the bootloop went all the way through Google splashscreen. After plenty of mucking around, now it couldn't pass through Google logo.
I tried to flash the phone with 4.0.4 to no available. It kept saying 'Sending bootloader: failed (status read: failed)' or 'Sending bootloader: failed (remote: write fail)'.
I'm wondering if actually the device has to be rooted first in order to flash a phone. How could I root it if it's already stuck in bootloop?
PS: I tried flashing using mskip's tool, wug's etc. The pc detected the phone in fastboot mode. I could see the numbers.
Any help is appreciated. Thanks a lot.
If your bootloader is still locked, you won't be able to flash. Keep in mind that to flash the 4.0.4 update manually using fastboot, you need to unlock the bootloader. Doing so will wipe data/factory reset the phone causing you to lose everything in your internal storage.
Command to unlock the bootloader - fastboot oem unlock
follow link below for instructions on flashing a stock image.
http://forum.xda-developers.com/showthread.php?t=1366806
the guide specifies up to ICL53F, you can actually use the commands he states in the guide but replace the file names with those of the stock IMM76I image directly from google. Location of stock google images (yakju) https://developers.google.com/android/nexus/images
I hope this helps you in some way.
I forgot to say I had already unlocked the bootloader. However it's still unrooted if it does matter.
Thanks for posting the link though.
It shouldn't matter if you're unrooted. If you try the commands in one of the links I sent, it should work.
Okay, will try this later and I'll get back to you. Thanks a lot.
Hi racerklm,
I tried your method and it failed.
When I entered the first command, the result was as follows:
Sending bootloader ......... OKAY
writing bootloader ......... Failed (remote: write fail)
I just don't get what this means. Does anyone know what this is about? Any help is really appreciated.
Are you on a GSM or CDMA gnex? Just to clarify things. If you're on a GSM version the below applies to you.
Did you download the Superboot zip from the first thread i linked you? You need to extract both the r4-galaxynexus-gsm-superboot.zip and the IMM76I.zip you downloaded from google.
Look for the following files inside the IMM76I.zip you downloaded from google and transfer them to the same directory as fastboot.
bootloader-maguro-primela03.img
radio-maguro-i9250xxla2.img
image-yakju-imm76i.zip
Once that's done, do the following commands (taken from thread I linked you).
fastboot-windows flash bootloader bootloader-maguro-primela03.img
fastboot-windows reboot-bootloader
fastboot-windows flash radio radio-maguro-i9250xxla2.img
fastboot-windows reboot-bootloader
fastboot-windows -w update image-yakju-imm76i.zip
if you're on mac or linux just replace "windows" in the commands with "linux" or "mac"
I'm using a GSM model. I did download the superboot zip and the stock google image.zip and extracted all of their files into the same folder.
I have also already typed the first fastboot command. However those words came up again. The very exact words when I tried to fix the device using mskip's and wug's tool. I also tried using two other Windows PC and one Mac PC to no avail. Haven't tried linux since I don't have one.
Your posts are very informative, I thank you a lot for that. However it just didn't work in my case. I've read plenty of similar threads. Their devices could get back to normal. Mine doesn't. I don't know why. Hence, I really wonder what 'remote: write fail' means.
Sorry that there's nothing I can do to help you solve this problem. Have you tried just running the last command? fastboot-windows -w update image-yakju-imm76i.zip? If somehow you can get that flashed, it should boot up normally.
I tried that just now and this came up:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEKK15
Baseband Version.....: I9250XXKK6
Serial Number........: xxxxxxxxxxxxxxxxx
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
checking version-baseband... OKAY
sending 'boot' (4148 KB)... OKAY
writing 'boot'... FAILED (status read failed (Too many open files in system))
Long time ago I could get into recovery mode and playing around with the device. I wonder if I accidentally unmount the sd? Now I could no longer get into recovery mode. When I select recovery, it would just go to the Google logo with lock image at the bottom.
hmm try flash clockwork recovery and see if that works?
If it's refusing to flash valid files from fastboot, you may just have a hardware defect. Relock the bootloader and if you can still produce the bootloop symptoms, take it for warranty.
I can boot into CWM but not flash it. Is there anything else I could do before sending it in for warranty/fixing?
most likely then it's a hardware defect. best to take it in for warranty work.
wsoelivan said:
I can boot into CWM but not flash it. Is there anything else I could do before sending it in for warranty/fixing?
Click to expand...
Click to collapse
The first thing I would try is to change USB cables.
Next I would try changing USB ports on your PC. Use the ones at the back, not the front.
If that still doesn't work, and you have CWM installed, you could always flash back to stock while booted in CWM (assuming your PC sees your device when booted in CWM).
Crazy as it sounds, you may also want to check your USB cable.
When I worked as Swype's tester, I flashed perhaps hundreds of ROMs across many different devices. In particular I remember having a similar problem with a particular prereleased device, and swapping the USB cable seemingly fixed the problem on more than one occasion. I studied EE in school, and I never could explain why this was a problem or why this would fix it.
Sent from my Galaxy Nexus using XDA
efrant said:
The first thing I would try is to change USB cables.
Next I would try changing USB ports on your PC. Use the ones at the back, not the front.
If that still doesn't work, and you have CWM installed, you could always flash back to stock while booted in CWM (assuming your PC sees your device when booted in CWM).
Click to expand...
Click to collapse
I have already tried 3 different USB cables and all ports in my PC. But, I'm gonna give it one more try for the last time.
I don't have CWM installed, I could only boot it from mskip's tools.
Chinpokomon said:
Crazy as it sounds, you may also want to check your USB cable.
When I worked as Swype's tester, I flashed perhaps hundreds of ROMs across many different devices. In particular I remember having a similar problem with a particular prereleased device, and swapping the USB cable seemingly fixed the problem on more than one occasion. I studied EE in school, and I never could explain why this was a problem or why this would fix it.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
At first I was using two Blackberry's USB cables and it didn't work. Then I read in the forum suggesting to use the original cable. I became very hopeful and suddenly grabbed the USB cable came with the phone.
However, as I said before, I might probably try this method one more time. I'm gonna install a linux OS first and try again before sending it in.
On the other hand, I've tried another method of flashing using ODIN mode. Not surprised at all, it still didn't work.

[Solved] Several (related) problems flashing anything but stock

I have a C6506 that is unlocked, have checked via the service code. Not just unlockable but unlocked. Certain.
I've used both older flashtool64 that worked before (0.9.11.0) on a Surface Pro (windows 10) and newer (0.9.19.10) on a desktop (Windows 10 also).
In both cases I can flash 10.7.a.0.222 for C6506. I also can flash 10.3.a.0.423 on the Surface (did not try on others). It boots, it works, no issues.
I can get in fastboot mode on the phone (blue light), but on the surface with the older Flashtools (and associated drivers) I cannot access the phone at all, just waiting for device.
On the newer flash tools with drivers installed (turned off signing verification) I can get into fastboot and do things like a "getvar version", but I cannot do more complex things like get the unlock status, nor can I flash a boot image (in this case from CM 12.1). It says "Command not allowed" in the write phase. Yes, the phone is unlocked, really, at least it says it is, and I did do an unlock code with legitimate Sony provided codes. And previously rooted using it as unlocked.
I've also tried getting root with a pre-rooted 10.7.a.0.222 -- I can get an older version rooted, put recovery on it, I can do the install of the zip and it completes -- then boot loop. This is using Beta-SuperSU-V2.52.zip and zl-lockeddualrecovery2.8.23-release.combined.zip with PRFCreator. (The recovery is also what I used to do the install). Boot loop. Can't get out of it without a new flash despite power off, resets, etc. Can't get back into recovery either at that point.
I do have the phone working with a non-rooted stock Sony 10.7.A.0.222. As mentioned, flashes fine. I just can't seem to get CM running (can't fastboot the boot image), nor can I get root on the stock sony (boot loop).
I've also tried the fastboot program on the current SDK as well as the one in Flashtools without any difference, still can't flash a boot.img from cm12.1.
I feel like I'm missing something fundamental, like maybe some aspect of running Windows 10 that is interfering (I have no older version currently). I'd suspect CM12.1 but it also is failing with the typical root technique for 5.1.1 stock (i.e. root older version first).
While I am not an active developer, this is not my first round of flashing or updating the phone, though it is my first round in a year or more, certainly since Windows 10.
I realize this is a lot like "nothing is working what could be wrong" and not a very specific question, but wondering if anyone has any suggestions as to whether there might be a common cause here.
I do have one more interesting piece of information that I do not understand.
I downloaded Emma and tried to use it to flash stock just to make sure the image I had was good for stock.
Emma says "this phone is locked". So thinking my last flash re-locked it, I went into flash tools and did this:
U:\AndroidSDK\platform-tools>fastboot oem unlock 0xkey-from-sony
...
OKAY [ 2.969s]
finished. total time: 2.969s
After doing so, Emma STILL says it is locked.
Flash tool however allows me to flash it.
Any clue why Emma would say "locked" when I just finished unlocking it?
In service, configuration it says "Yes" to unlocked, not "no/yes" or any other combination, just "yes".
focus on getting the sdk tools to work, like fastboot. What do you mean it just does not flash( show console output of your fastboot flash boot boot.img), Is fastboot not recognized in the device manager, It is odd you can use it to 'oem unlock'... I had to change driver files when I switched from windows 7 to windows 10. if you can 'fastboot devices' and 'adb devices' you should be good to go as far as flashing, maybe you have bad images not made for the phone? I am no pro take my information with a grain of salt.
ham5 said:
focus on getting the sdk tools to work, like fastboot. What do you mean it just does not flash( show console output of your fastboot flash boot boot.img), Is fastboot not recognized in the device manager, It is odd you can use it to 'oem unlock'... I had to change driver files when I switched from windows 7 to windows 10. if you can 'fastboot devices' and 'adb devices' you should be good to go as far as flashing, maybe you have bad images not made for the phone? I am no pro take my information with a grain of salt.
Click to expand...
Click to collapse
I will try again tomorrow (need the phone tonight and it takes a while to get stock back up and configured).
Concentrating on fastbook and on my more-working desktop (the tablet definitely has some issue, I think driver related).
I installed the newest Flashtools, and also installed the fastboot and s1 drivers from it (I think that's what they are called). I configured Windows to permit them unsigned and they installed without error.
When I try to do CM12.1, what I did was download their distribution zip, and unzip it and pull out the boot.img file. I then put the phone in fastboot mode, and it worked and was recognized (e.g. "fastboot getvar version" responds).
Going by the instructions for CM12.1, I then tried to do "fastboot flash boot c:\pathwhereitwas\boot.img"
This does a send of the file, which works, and then does a write and says "command not allowed". So it appears to transmit the file but can't commit it to flash. I cannot post the log as didn't save it but if you think relevant can post tomorrow.
As to the locked issue -- after trying this the first time, I thought "maybe the phone has been locked again". So I did the #*#*service*#*# and see it says "yes" for unlocked. But just to be safe, I dug out my 2 year old email from Sony and did another unlock. As to why I did it with the "oem unlock" that's how CM12.1 suggests (https://wiki.cyanogenmod.org/w/Install_CM_for_odin). The first time I typed it, it failed, the second time it said "OK". Tried the flash boot again, same "command not allowed error".
The phone goes into fastboot mode easily (blue light, plus response to things like getvar). It goes into flash mode fine also, and indeed, after I gave up (each of several times) I flashed stock back on the phone and it came up with 5.1.1 stock.
I wanted to run CM12.1 as I really don't like that stock has not patched stagefright, plus I hate not having root.
Any suggestions what I may be doing wrong, that fastboot commands sometimes work, but I can't flash the boot file?
Am I flashing the RIGHT boot file? Should I be flashing the CM12.1 recovery image they have on their download page instead? (But the instructions are pretty clear).
I should note that the phone does not appear to have a recovery on it -- booting after flashing stock, and toggling all the volume buttons in any combination is just ignored.
I think your really digging way to deep into this...
The phone goes into fastboot mode easily (blue light, plus response to things like getvar). It goes into flash mode fine also, and indeed, after I gave up (each of several times) I flashed stock back on the phone and it came up with 5.1.1 stock.
Click to expand...
Click to collapse
what is the difference between fastboot and flash mode? Ive never heard of this flash mode....
This does a send of the file, which works, and then does a write and says "command not allowed". So it appears to transmit the file but can't commit it to flash. I cannot post the log as didn't save it but if you think relevant can post tomorrow.
Click to expand...
Click to collapse
I don't believe it sends a file at all, it is flashed/written to the boot partition right away.. or is supposed to - I would consider this your chief complaint... "command not allowed" when trying to fastboot flash a boot.img -- I get a lot of hits googling that.. driver problems/bootloader locked
ham5 said:
I think your really digging way to deep into this...
Click to expand...
Click to collapse
I'd welcome a shorter, simpler path.
ham5 said:
what is the difference between fastboot and flash mode? Ive never heard of this flash mode....
Click to expand...
Click to collapse
Perhaps it is purely a sony thing. If, with the phone powered off, you plug it in holding the volume up button you end up in fastboot mode; if you plug it in with the volume down you end up in flash mode.
Flashmode is used by Emma and by Flashtools. Fastboot is used by the Fastboot utility. I'm unclear what happens under the cover, but they are not interchangeable.
ham5 said:
I don't believe it sends a file at all, it is flashed/written to the boot partition right away.. or is supposed to - I would consider this your chief complaint... "command not allowed" when trying to fastboot flash a boot.img -- I get a lot of hits googling that.. driver problems/bootloader locked
Click to expand...
Click to collapse
As I said, I do not know what happens under the covers, but in fastboot mode when you do the "flash boot" it first says it transmitted a file (shows bytes sent, etc) then it does a "write" command itself and it is that write command that fails.
And therein lies my issue trying to flash the boot image -- the write command fails, and I cannot figure out why.
Drivers: I've tried the latest flashtool, and installed the drivers from there. They do install (with signing verification off), and they do connect and see the phone. Some commands work, but this one does not. Could it be the drivers? Certainly, but I do not know what to try to fix them.
Emma: I hate to keep coming back to this, but I do not understand why Emma says my phone is locked, when it clearly appears not to be. I've both re-unlocked it, confirmed it is unlocked with the service menu. But that it thinks it is locked, and the "write" command failure, makes me wonder if there is an issue either in the phone or windows or drivers that makes it act that way. incidentally I've also tried all this with antivirus/firewalls off with no effect.
Locked: just to confirm, in the service menu it says "Root Status" and "unlockable" as "yes". Not "Yes/no". That means it is currently unlocked, correct?
To your first point, I may be over-complicating it. I would welcome some suggestion of other simpler steps. I've done the same google, and don't see real solutions other than "try better drivers", but most threads seem to point to the flashtools drivers, and I've tried those, as well as installing Emma which (presumably) either used those or loaded its own.
Incidentally if this is more appropriate to the Q&A forum, and a moderator is handy, I would appreciate it moving. I placed it here because this relates mostly to the Flashtools drivers and the process of using fastboot.
I cant say for sure .. CM's dialer does not work with service menu... but you defiantly not worried about root... your looking for the bootloader to be unlocked, not unlockable..
ham5 said:
I cant say for sure .. CM's dialer does not work with service menu... but you defiantly not worried about root... your looking for the bootloader to be unlocked, not unlockable..
Click to expand...
Click to collapse
I've never gotten to CM on this phone so that's moot. I'm doing the service menu from the stock phone. And so far as I can tell the bootloader is unlocked.
I went back to a much older version of Flashtools (0.9.11) that dates from about the time I got the phone, but those drivers do not seem to install on Windows 10 at all.
But I'm not clear whether it is a driver problem, since some fastboot commands work fine.
Just read using emma with lollipop can screw your phone up... in fastboot mode can you 'fastboot getvar version' ?
here is the CM wiki - https://wiki.cyanogenmod.org/w/Install_CM_for_odin - good luck I don't think I can be of any help.
ham5 said:
Just read using emma with lollipop can screw your phone up... in fastboot mode can you 'fastboot getvar version' ?
here is the CM wiki - https://wiki.cyanogenmod.org/w/Install_CM_for_odin - good luck I don't think I can be of any help.
Click to expand...
Click to collapse
Yes, in fastboot mode I can do the getvar version. It says 0.5.
I had read the wiki; as mentioned that is why I was trying to flash boot.img.
As requested here is a fastboot session log:
Code:
U:\AndroidSDK\platform-tools>fastboot getvar version
version: 0.5
finished. total time: 0.002s
U:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (10668 KB)...
OKAY [ 0.340s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.340s
U:\AndroidSDK\platform-tools>fastboot flashing get_unlock_ability
...
^C
U:\AndroidSDK\platform-tools>fastboot devices -l
EPxxxxx47K fastboot
U:\AndroidSDK\platform-tools>fastboot devices
EPxxxxx47K fastboot
U:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (10668 KB)...
OKAY [ 0.340s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.354s
U:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (10668 KB)...
OKAY [ 0.340s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.353s
As you can see some commands work, some do not. Not sure the get_unlock_ability is even supposed to work as it looks like a late comer to fastboot and the phone is old.
Most articles I find posted about "command not allowed" do not seem to get as far as being able to use fastboot at all, but even if it is a driver issue, not sure what I can do about it, these are the latest drivers.
Ok, I've managed to get this to work. I can tell you what I did, but not why, but in case it helped someone else.
The bootloader showed unlocked, but I ran the flashtool option to unlock it again, then WITHOUT REBOOTING I did the fastboot option to flash the boot.img.
It appears that if you reboot (to stock) in between, it does something that at least makes it appear the bootloader is locked (the service menu shows it NOT locked still).
There's another thread here that implies you need to do it multiple times, but I think the issue is not a need to do it more than once, but a need to make sure that (at least a late version stock) does not get a chance to run, as it appears to do something.
I'm now happily on 12.1. Well, sort of happy, I finally noticed it says it doesn't support the 6506 (as opposed to the 6503) so I might not stay long, but at least I worked out what was wrong. Thanks to those who encouraged me to keep looking.

Soft-bricked MediaPad M2 803L

Hi everyone,
It seems I was stupid enough to choose a wrong model (MediaPad M1) in TWRP Manager (downloaded from Google Play) while attempting to install TWRP recovery.
This resulted in an infinite bootloop where the "Huawei MediaPad" logo keeps appearing, the tablet restarts and again the same.
I do have access in Recovery and Bootloader mode, but all my attempts did not yield any results. Things I have tried so far:
- Download the Stock ROM from needrom.com (versions B009 and B019), extracted them and loaded the "dload" folder onto an SD card and executed recovery (by pressing both Vol UP/DOWN and starting the tablet). Even though the procedure seems to be perfoming normally, indicator reached successfully 100%, when the tablet restarts after the supposed successful recovery I am still left with the same bootloop.
My SD is a 64GB one, formatted with exFAT if this makes any difference.
- I have tried extracting UPDATE.APP using Huawei Update Extractor (http://forum.xda-developers.com/showthread.php?t=2433454) and tried to push via fastboot all necessary parts (i.e. BOOT.img, RECOVERY.img, SYSTEM.img, etc) but I get the "FAILED (remote: Command not allowed)" error message.
My bootloader was unlocked from the beginning (at least that's what showing when I enter bootleader/rescue mode with red letters - "PHONE UNLOCKED").
Any suggestions would be greatly appreciated! Thanks!
What commands are you using? It is peculiar that fastboot mode fails to flash. It may be that your bootloader is not properly unlocked even though it shows that it is.
If you have a bootloader unlock code for your device, I would suggest that you try explicitly unlocking the bootloader when in fastboot mode (it won't hurt to do this even if your bootloader is already unlocked):
Code:
fastboot oem unlock <YOUR_BOOTLOADER_UNLOCK_CODE>
Then you can verify that the bootloader is actually unlocked by issuing the following command:
Code:
fastboot oem get-bootinfo
If your bootloader is properly unlocked, then the previous command should return output similar to the following:
Code:
(bootloader) unlocked
OKAY [ 0.001s]
finished. total time: 0.002s
At this point, let's try to restore your original BOOT partition and RECOVERY partition.
Now, gather the following partition images from your OEM firmware package:
BOOT.img
RECOVERY.img
SYSTEM.img
USERDATA.img
Only BOOT.img and RECOVERY.img should be needed to solve your issue, but we'll have SYSTEM.img and USERDATA.img ready and available here just in case our efforts fail with just boot and recovery alone.
Now erase and flash boot and recovery as follows (replace /path/to/oem/ in the commands below with the full path to the files you extracted from your OEM firmware):
Code:
fastboot erase recovery
fastboot erase boot
fastboot flash recovery </path/to/oem/RECOVERY.img>
fastboot flash boot </path/to/oem/BOOT.IMG>
fastboot erase cache
fastboot reboot
Hopefully, at this point your bootloop issue is resolved and your ROM boots normally. If not, then read on.
Uh oh, time to flash SYSTEM.img and USERDATA.img too and see if that makes a difference. While we're at it, let's also reflash BOOT.img and RECOVERY.img. Use the following commands (replace /path/to/oem/ in the commands below with the full path to the files you extracted from your OEM firmware):
Code:
fastboot erase recovery
fastboot erase boot
fastboot erase system -w
fastboot flash recovery </path/to/oem/RECOVERY.img>
fastboot flash boot </path/to/oem/BOOT.IMG>
fastboot flash userdata </path/to/oem/USERDATA.IMG>
fastboot flash system </path/to/oem/SYSTEM.IMG>
fastboot erase cache
fastboot reboot
...and hopefully now you're back up and running.
Good luck!
In case you don't have a unlock code and *already* bricked it, you can get the imei from fastboot as well. Simply send the following command from fastboot:
fastboot oem get-psid
Using the imei you can then request an unlock code from huawei on their web site.
Thank you both for replying!
Unfortunately, I don’t have an unlock code. I have contacted Huawei through https://emui.huawei.com/en/plugin.php?id=unlock&mod=detail months ago asking them for an unlock code for the bootloader but I never got a reply. I have even tried again a couple of months ago but they didn’t answer back. It seems there is a limitation on the time entitled to ask for an unlock code – I believe 3 or 6 months if I remember correctly.
I have just tried contacting them again through an e-mail form, let’s hope this time they’ll reply.
Now please allow me to fill you up in some more test/trials I did today:
I issued the “fastboot oem get-bootinfo command” and the result is this:
(bootloader) unlocked
OKAY [ -0.000s]
finished. total time: -0.000s
(Not even a milisecond in replying. This looks a bit suspicious, right?)
But when I try to continue as per your instructions (i.e. issue the command “fastboot erase recovery”) this is what I get:
erasing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: -0.000s
So I cannot go on using your suggestions
I have also tried to use DC-Unlocker to unlock the bootloader (perhaps wasted money since the bootloader is already unlocked but I just wanted to try). When I bought the credits and opened DC Unlocker Client, the option for Unlock was grayed out, but the option for Factory Reset Protection was selectable. Based on this, I am now suspecting that the tablet has got FRP protection enabled, since I did have a PIN set-up before choosing the wrong model in TWRP manager and brick it. So I tried DC Unlocker’s Factory Reset Protection (paid 15 wasted euros!) but again no luck. This is the log from that attempt:
===================================================================
Before detection Huawei Android phones, enable 'Manufacture' mode:
in dial pad type *#*#2846579#*#* for Qualcomm and Kirin based models, or *#*#14789632#*#* for MTK, then select
'ProjectMenu',
'Background settings',
'USB ports settings',
'Manufacture mode'.
Step by step guide for other Huawei phone unlock:
https://www.dc-unlocker.com/huawei_phones_detect_unlock_tutorials
===================================================================
DC - Unlocker 2 Client 1.00.1322
Detecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Phone : HUAWEI M2-803L
Model : Huawei phone in fastboot mode
Serial NR. : YVF4C15928000296
Firmware : V100R001C00B000
unlocked
Battery state: 3648mv
===================================================================
Factory reset protection Erase start
unknown error (398)
===================================================================
Since I already paid the €15 at DC Unlocker I decided to give a go using their other piece of software, DC Phoenix. This one allowed me to flash pieces of the UPDATE.app package while in fastboot mode, without complaining about locks. It seemed to be flasing normally (I tried flashing all contents of the latest UPDATE.app package) and then (as per DC’s instructions) I tried re-flashing everything using the second option (Upgrade Mode) while in Repair mode (i.e. Vol +/- pressed while powering the tablet).
No success either – Tried various combination of DC Phoenix – even only the files you suggested (BOOT & RECOVERY, BOOT & RECOVERY & USERDATA & SYSTEM).
Is there a way to find out if FRP has been activated through fastboot? Tried Googling it but no usable results came up.
Any other suggestions would really, really be appreciated!
manowar666 said:
Thank you both for replying!
Unfortunately, I don’t have an unlock code. I have contacted Huawei through https://emui.huawei.com/en/plugin.php?id=unlock&mod=detail months ago asking them for an unlock code for the bootloader but I never got a reply. I have even tried again a couple of months ago but they didn’t answer back. It seems there is a limitation on the time entitled to ask for an unlock code – I believe 3 or 6 months if I remember correctly.
I have just tried contacting them again through an e-mail form, let’s hope this time they’ll reply.
Click to expand...
Click to collapse
I did contact Huawei for an unlock code, myself - I sent emails to [email protected] and [email protected] and received a reply back from them the next day. Here is what they said:
Dear User,
Huawei Customer Service is pleased to be at your service.
Apology for any inconvenience.
If you would want to unlock your phone, you should meet the following conditions:
1.Please register your Huawei ID in our official website http://emui.huawei.com/en/ on your phone.
2.Log in your Huawei ID continuously for 14 days.
3.Each Huawei ID should not apply for the unlock code more than twice within 6 months.If you meet the criteria,please go to http://emui.huawei.com/en/ and click the 'download'button to login your Huawei ID other than any other third party ID to apply for the unlock code.Please contact us by mail or local service hotline as following if error message appears.
TEL: http://consumer.huawei.com/en/contact-us/index.htm?tag=hotline
Mail: http://consumer.huawei.com/en/contact-us/index.htm?tag=email
Please submit your mobile model, SN, IMEI/MEID and erro message in your e-mail.We also need to know that your phone is rooted, it can be out of the best working state and some of the functions may not be able to work normally. In additon, the system is vulnerable to be invaded by viruses once your phone is permitted to unlock. For the lack of testing,third party software may not be compatible with your phone. Unlocking will bring unexpected negative impacts and the device will be not normal, and can not be restored, Huawei after-sales service office will not provide warranty service for your rooted phone, and you may bear the cost. So we strongly advise you to think twice.
If you have any other problems, please send your feedback to us. We will be at your service to help you to solve your problems.
Once again thank you for contacting Huawei device.
Best Regards.
Huawei Device Customer Care Team
Click to expand...
Click to collapse
I didn't want to faff around with all that logging in nonsense for two weeks, and also the Huawei bootloader code site seemed to be offline (kept getting "Page not found" errors with the error page in Chinese characters and what was ostensibly an HTTP 600 error, which was why I contacted Huawei support over email), so I just ponied up about $4.25 for 4 dc-unlocker credits (4 euros) and got my bootloader unlock code from the dc-unlocker software. Neat, clean, easy and non-messy.
manowar666 said:
Now please allow me to fill you up in some more test/trials I did today:
I issued the “fastboot oem get-bootinfo command” and the result is this:
(bootloader) unlocked
OKAY [ -0.000s]
finished. total time: -0.000s
(Not even a milisecond in replying. This looks a bit suspicious, right?)
Click to expand...
Click to collapse
Yes, that does seem very odd. I would expect it to take at least some time in userspace (the "total time" field).
manowar666 said:
But when I try to continue as per your instructions (i.e. issue the command “fastboot erase recovery”) this is what I get:
erasing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: -0.000s
So I cannot go on using your suggestions
I have also tried to use DC-Unlocker to unlock the bootloader (perhaps wasted money since the bootloader is already unlocked but I just wanted to try). When I bought the credits and opened DC Unlocker Client, the option for Unlock was grayed out, but the option for Factory Reset Protection was selectable. Based on this, I am now suspecting that the tablet has got FRP protection enabled, since I did have a PIN set-up before choosing the wrong model in TWRP manager and brick it. So I tried DC Unlocker’s Factory Reset Protection (paid 15 wasted euros!) but again no luck.
Click to expand...
Click to collapse
I find it very peculiar that your bootloader is unlocked but FRP is activated. I think that dc-unlocker does not give you the option to unlock the bootloader because FRP protection is still active - according to all guides, FRP must first be deactivated if you want to unlock the bootloader.
What does your phone say in the bootloader screen for the FRP? You'll find it directly under the "Phone Unlocked" text. It should say either "FRP Locked" in green or "FRP Unlock" in red.
manowar666 said:
Is there a way to find out if FRP has been activated through fastboot? Tried Googling it but no usable results came up.
Any other suggestions would really, really be appreciated!
Click to expand...
Click to collapse
There isn't, directly, but you can try to issue the fastboot command
Code:
fastboot oem frp-erase
although at this point I am not very hopeful that it will work.
FRP is nothing but the developer option to allow an OEM unlock of the phone - it is the option mentioned in this image in the Huawei "Unlock bootloader" guide thread.
Like I said, I find it very peculiar that FRP is enabled but the bootloader is "unlocked". Did you at any point reset the developer options or reflash the stock ROM before you soft-bricked the device? Did you pick up this phone second-hand/used or something?
I think that the root (excuse me, I couldn't resist) of all your problems is that FRP is still enabled, and this is what is causing your flash attempts to fail.
Here is the dc-unlocker guide to repair a bricked Huawei phone even if the bootloader and FRP are locked. If you follow this guide very carefully, maybe it can save you. Since you already seem to have tried "Method 1" of the guide, maybe you can try "Method 2".
Another suggestion I have is that you can contact the dc-unlocker guys for online chat support (when you see that the chat is online). They are very helpful, and since you've thrown so much money at them (be sure to mention that, just in case they don't know), they should be able to do something to help you out. Good luck, and I hope that you can get your phone back online...
I've been faced with all the same issues as the OP for the last 24 hours and thought all was lost. I had been through all the same stuff - every fastboot command and every key combination possible. I'd tried different tools and apps to get some life out of the device but no luck. I had even downloaded the ROM from beast.in.black's thread and extracted it to the SD card but it didn't do anything for me.
Worse still, the tablet was now out of juice. And as soon as I plugged it into the mains, the screen lit up and the all too familiar fastboot screen would stay on, meaning the tablet was barely charging long enough for me to try anything new with adb / fastboot or whatever.
So in trying to get the screen off and charge the tablet, while it was plugged in I held vol up / vol down / power together for 10 seconds. I was hoping this would leave the screen off (I had managed this earlier while plugged into USB) but instead it booted again. So I walked away for a minute, then came back expected to see the fastboot screen but no, it was in the middle of an EMUI software install. Huzzah! I left it to do its thing but at the end, it came up and said install failed and my only option was to press power to reboot. Sigh. So I pressed power and then got another surprise. The Huawei boot logo. The tablet was booting. A few seconds later I'm at the "Choose your regional settings & language" screen in the setup wizard. After trying everything under the sun, it turns out all I needed was the ROM on the SD card and to give the tablet the three-finger-salute while plugged into mains.
Happy days!
I found the Official M2-803L ROM!
For anyone who needs it, I've found an official download (direct from the Huawei China support site) for the M2-803L.
I've posted the ROM details here for anyone who needs this ROM.
Status update for anyone that might be interested: I was able to restore the tablet with the help of DC-Unlocker. I highly recommend them for any unlocking/restoring needs.
More specifically, I contected them via email and they were kind enough to give me credits (since I already paid them) in order to try again with Method 2 as per https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Step 2 of this method did not work for me (i.e. flashing in upgrade mode) but I was able to replace this step simply by re-flashing with DC Phoenix in fastboot mode.
After this, my IMEI was zeroed-out (that was a problem since this tablet is 4G-enabled thus I couldn't register on my provider's network) but I was also to fix that by using HCU-Client (had to purchase 8 more credits from DC-Unlocker).
All are working fine now.
Special thanks to @beast.in.black for pointing me towards the right direction!

X2 Pro: "Your device is corrupt. It can’t be trusted and may not work properly."

X2 Pro: "Your device is corrupt. It can’t be trusted and may not work properly."
Hi everybody,
my Aquaris X2 Pro worked fine with rooted BQ 1.7.3 firmware (Android 8.1 based) - Magisk was installed and worked fine and also the xposed framework.
Today the device was normally working as it suddenly just reboots
After that the usual "unlocked bootloader" screen appears but then it only shows a screen with the message "Your device is corrupt. It can’t be trusted and may not work properly."
I can select "continue" - but that only leads back to the "unlocked bootloader" warning screen --> a boot loop :crying:
Does anybody know how I can bring back my device back to work - without losing all my settings and stuff?
And any idea what happened (so that I can prevent it to do so in future)?
Hmm, I'm not 100% sure, but I think I saw that message / boot process once as I tried to root my X2 Pro.
I had done a
Code:
fastboot flashing unlock / unlock-critical
but no
Code:
fastboot oem unlock
(or the other way round? Definitely only done one of them - I was following instructions from a thread here)
and was trying to boot a magisk patched boot-img via
Code:
fastboot boot magisk_patched.img
So, it looked like the bootloader was "NOT fully" unlocked and it detected booting a "not correctly signed" bootloader.
Perhaps check your unlock status via
Code:
fastboot getvar all
But note - UNLOCKING again will wipe your data ... and can only be done if the setting in developer options is active (I fear that THAT may have changed on your device)
You could also try booting the second slot
Code:
fastboot getvar current-slot
and then
Code:
fastboot set_active a/b
(if current-slot gives a, boot b and vica versa).
Last idea: try flashing ONLY the stock boot.img. If you can do this, this should re-enable you to boot. You will loose root, but may be able to backup (most) of your settings via Helium
Thanks a lot for your help!
Inbetween I had to go the hard way and reflashed the newest BQ factory image v2.0.2 (based on Android 9) to both parts _a and _b - losing all my data...
after that I patched the boot.img for magisk and reflashed that to my _a boot partition (and still have the original boot.img in _b).
It did cost me a bit of my spare time - but it wasn't as hard as I expected...
I was able to restore a lot of my settings with Titanium backup....
merlinwv said:
I had done a
Code:
fastboot flashing unlock / unlock-critical
but no
Code:
fastboot oem unlock
Click to expand...
Click to collapse
That was exactly what I did - the first time I only did a "flashing unlock", no "unlock-critical" - so now I had to do it to flash the complete factory image, and therefore it wiped all my data again
merlinwv said:
I was following instructions from a thread here)
Click to expand...
Click to collapse
I used the BQ batch script to flash it, but did not execute the erase commands.
But that did not help to keep my data as I needed to execute a "unlock-critical"...
merlinwv said:
So, it looked like the bootloader was "NOT fully" unlocked and it detected booting a "not correctly signed" bootloader.
Click to expand...
Click to collapse
Hmm, it worked for several months without problems - don't know why it suddenly complained about it.
merlinwv said:
Perhaps check your unlock status via
Code:
fastboot getvar all
Code:
fastboot getvar current-slot
Click to expand...
Click to collapse
Very interesting commands which I didn't know - I already wondered how I can get that information
merlinwv said:
Last idea: try flashing ONLY the stock boot.img. If you can do this, this should re-enable you to boot. You will loose root, but may be able to backup (most) of your settings via Helium
Click to expand...
Click to collapse
That would be a great idea :good: which I could've tried - but I didn't...; maybe next time - although I hope the problem will never come back
Bodenseematze said:
Thanks a lot for your help!
...
I used the BQ batch script to flash it, but did not execute the erase commands.
But that did not help to keep my data as I needed to execute a "unlock-critical"...
Click to expand...
Click to collapse
You are most welcome
The erase commands are not the ones doing the factory-reset - if you want to keep your data during a "factory-flash" you need to comment/delete the lines which flash the userdata-partition.
But I do not know if you can flash the factory image without unlocked critical (=boot) flashing. I never tried this myself. Some phones allow flashing of correctly signed boot images even when critical is locked, others prevent ALL flashing then.
Of course, for "he who knows what he is doing" there is always the possibility to flash in EDL-mode (turn off, afterwards keep vol+, Vol- and Power pressed - will bring you to a special flash mode that allows flashing even when locked - but via a special serial interface etc. pp.). Google it - this would have helped you regarding "loose of userdata when doing unlock critical". But of course - you need to edit the file because in EDL mode, normally userdata is flashed, too.
Just something to keep in mind for the next time
Hmm, it worked for several months without problems - don't know why it suddenly complained about it.
That would be a great idea :good: which I could've tried - but I didn't...; maybe next time - although I hope the problem will never come back
Click to expand...
Click to collapse
I think that perhaps an update was installed (explanation for the reboot?!) that switched to the other boot-slot and did a more thorough check of the boot-chain. This was the reason to suggest trying the other boot-slot (which would then be the pre-update version, that may still boot - and even have root)
merlinwv said:
Of course, for "he who knows what he is doing" there is always the possibility to flash in EDL-mode
Click to expand...
Click to collapse
Again: very interesting information! :good:
merlinwv said:
I think that perhaps an update was installed (explanation for the reboot?!)
Click to expand...
Click to collapse
I hope that wasn't the reason, because I explicitly switched off all automatic updates. And I did not do a manual update!
merlinwv said:
that switched to the other boot-slot and did a more thorough check of the boot-chain. This was the reason to suggest trying the other boot-slot (which would then be the pre-update version, that may still boot - and even have root)
Click to expand...
Click to collapse
I tried to switch to the other slot and boot it - but that didn't help either and led to the same problem...
What I didn't tried was to only flash the boot.img - will do this next time

Categories

Resources