Database Develop

[Q] Milestone bricked? (boot loops, bootloader error)

Hello guys,
I hope you get not bored by these every day "I bricked my milestone" threads, but I do really need and would appreciate your help. So here is what's going on:
After Motorola delays the official 2.2 ROM again I decides to try CM6. I asked a friend, who has flashed his Milestone before, for an instruction and he gave me one.
I had an Milestone from O2 Germany with latest 2.36 update. First I made the recovery vulnerable. I downgraded to 2.34 and flashed the vulnerable-recovery only (of course the one for my 90.78 bootloader). I checked if the system was working right after every flash via RSD, and the phone bootet properly anytime. I applied the Androidiani update.zip and entered the OR. I wiped and applied the CM update via OR.
After I applied the CM update, the OR told me to reboot and so I did. I saw the Motorola logo and then the bootloader came up with an error message (Err:A5,70,39,00,27). I wanted to restore via Nandroid, but I no longer could enter the recovery (not to mention the OR). So I asked my friend again what to do and he told me to flash vulnerable recovery again via RSD (yes, I could enter bootloader mode) to be able to enter recovery again. After I flashed I could enter the recovery, but some new mad behavior appeared. The bootloader error disappeared, but every time I tried to boot, the phone ended up in boot loops (Motorola logo --> reboot --> Motorola logo --> reboot -->...).
Then I tried to restore via Nandroid. This seemed to work well, but after a reboot I got this bootloader error again.
To conclude:
flashing via RSD --> boot loops (recovery and bootloader work)
flashing via OR --> bootloader error (only bootloader works)
Some guy from android-hilfe.de told me to flash the bootloader, but I know this is very dangerous. So I went to the #milestone-modding irc-channel and asked for help. They gave me the advice to try to flash other sbf's, maybe an old 2.0. As I tried this today I got a new problem: the sbf file won't work. When I press 'start' in RSD everything starts as usual. But when the phone should show the message "sw update in progress" nothing happens and RSD get stuck on 0%. At the and I get the following message:
'ERROR: Flash failure: Phone[0000]: Error erasing subscriber unit. Device API Error: 0xE003003F Command: ERASE (Error Code: e003003f)'
So I did not proceed. Anybody a suggestion what to do? I'm really helpless.
Greetings Luke
PS: the forum search lead me to this thread. The problem sounds pretty similar.

Try flashing a 2.1 sbf. Let me know what happens. Please use RSDlite v4.6 or higher

vladstercr said:
Try flashing a 2.1 sbf. Let me know what happens. Please use RSDlite v4.6 or higher
Click to expand...
Click to collapse
Good advice. Latest rsd and drivers. Try a different machine...rsd is moody. Try the GOT sbf, it includes the vuln recovery. I have had problems with Win7 that got solved with a different machine with xp.
If all of this does not work, we need to try fastboot. But try the rest first...
Sent from my Milestone using Tapatalk

Hey, thanks for your replie
I did this 3 hours ago. I used the full sbf for the 2.36 update for the German o2 Milestone. I also tried DACH and other versions before.
The result is always, that I end up getting boot loops like described above. RSDLite tells me the file is successfully flashed and unlike a 2.0 sbf the Milestone shows the message "sw update in progress".
I'm using RSDLite 4.9.

LukeTS said:
Hey, thanks for your replie
I did this 3 hours ago. I used the full sbf for the 2.36 update for the German o2 Milestone. I also tried DACH and other versions before.
The result is always, that I end up getting boot loops like described above. RSDLite tells me the file is successfully flashed and unlike a 2.0 sbf the Milestone shows the message "sw update in progress".
I'm using RSDLite 4.9.
Click to expand...
Click to collapse
Try a different version of RSDlite on a different machine or operating system.

Caz666 said:
Good advice. Latest rsd and drivers. Try a different machine...rsd is moody. Try the GOT sbf, it includes the vuln recovery. I have had problems with Win7 that got solved with a different machine with xp.
If all of this does not work, we need to try fastboot. But try the rest first...
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
You mean a GOT 2.1 or the 2.2 sbf?
Unfortunately I have no machine running XP at the moment. But I have a virtual XP running on my Win 7 Pro. But I guess it's no good idea to try to flash on this?!

LukeTS said:
You mean a GOT 2.1 or the 2.2 sbf?
Unfortunately I have no machine running XP at the moment. But I have a virtual XP running on my Win 7 Pro. But I guess it's no good idea to try to flash on this?!
Click to expand...
Click to collapse
There is no GOT 2.1
GOT is only 2.2. You can try GOT 2.2 sbf and RSD v4.6

Oh, okay =)
I thought there is a version by them.
Gonna try your advices and post the results.
Thank you so far

Wow, your problem still same me.
I was tried and solved:
_Flash with any rom you have
_Milestone will auto reboot after flash done and loop
_Don't worry about that, remove battery in 5s and re-plugin
_Turn on your milestone: hold X and POWER to access Recovery. Select Wipe and reboot

killed said:
Wow, your problem still same me.
I was tried and solved:
_Flash with any rom you have
_Milestone will auto reboot after flash done and loop
_Don't worry about that, remove battery in 5s and re-plugin
_Turn on your milestone: hold X and POWER to access Recovery. Select Wipe and reboot
Click to expand...
Click to collapse
Did that before and tried it now. Didn't work for me. But thanks for your advice
I also flashed 2.2 from GOT. I was able to flash with RSD and it did not fail. But there is still the boot loop. So nothing changed.
This time I did it with my Atom-netbook and used RSD 4.6.

Ok, so I think I need to try something else. Only flashing with RSD easily doesn't work for me. Like I said in my post before: GOT 2.2 and the advice from killed did not work. Still getting boot loops.
So what would you recommend me to do?

LukeTS said:
Ok, so I think I need to try something else. Only flashing with RSD easily doesn't work for me. Like I said in my post before: GOT 2.2 and the advice from killed did not work. Still getting boot loops.
So what would you recommend me to do?
Click to expand...
Click to collapse
You tried GOT 2.2.1 sbf and it didn't work? Can you access recovery? There was a suggestion of fast boot, but I don't know what that is (just in case you wanted to google it or something, not sure). Do you have the drivers installed for your computer?
You could try this:
milestonefail said:
for some people RSDLite doesnt work properly. One way to fix that is put the SDL.bat file (attatched as .txt, change to .bat before using) in the RSDLite installation folder, move the .sbf file you are using to the same folder, and drag that .sbf to SDL.bat.
)
Click to expand...
Click to collapse
Read the end of this post: http://forum.xda-developers.com/showpost.php?p=11372663&postcount=51 Read the end
Also look here for the link for the drivers: http://forum.xda-developers.com/showpost.php?p=11163403&postcount=27
Good luck! I am not responsible if anything happens to your device.

Yep, it didn't work. RSD said the flash passed, but I always get boot loops. I can access th recovery, but even nandroid in OR doesn't work (I get back to that bootloader error I described in my first post).
I also don't know what fastboot is, but just using google won't help me, because I don't know, what I meant to do with fastboot.
The drivers are installed. Without them I guess RSD wouldn't even recognize my phone.
I also tried the batch file you posted, but it didn't work. I wasn't able to start the flashing process. I guess, the only thing the batch file does is to start RSD with admin rights.
These are all methods I tried and they just don't work. I need something different to this usual helpful stuff. That's why I posted in this forum, because I tried everything and I'm helpless at the moment.
Thanks for your advice anyway. I hope someone has a solution soon.

fastboot most likely will do nothing for you if a nandroid backup fails. Fastboot is a way to flash individiual partitions in case your recovery or nandroid does not work.
It works like adb (command line from a conected computer) and requires nothing on the phone. But if nandroid works...it will not do anything different.
Basically, a nandroid is a collection of .img files (one per partition) that a script flashes in sequence. With fastboot, you could flash all of the .img files from computer command prompt.
I would:
1) try a different nandroid...download the latest leak (01/25 from the dev forum). It is in nandroid format. I would factory reset the phone first.
2) if this does not work, i would fastboot erase and the fastboot flash (look up the syntax) every .img in the nandroid backup. This is just in case you OR is corrupted in some way...not likely, but i am out ideas.
Sent from my Milestone using Tapatalk

Hey,
thanks for your reply.
Your first recommendation would probably not work. I tried 4 different Nandroid backups and every time I get the bootloader error.
Basically I have no idea what fastboot is, where I get it from and not to mention how to get it work, so I think this is no option for me.
Right now I have resigned. Nothing seems to work. I consider getting a new phone. But before I do this I wanna ask you one last question: can flashing the bootloader theoretically effect anything? I think my phone IS bricked at the moment, so I'm not anymore afraid of flashing the bootloader. But if it would even theoretically be impossible, that this would change anything, then it's just a waste of time. So does flashing 90.78 bootloader via RSD Lite change anything?
Thank you!

LukeTS said:
Hey,
thanks for your reply.
Your first recommendation would probably not work. I tried 4 different Nandroid backups and every time I get the bootloader error.
Basically I have no idea what fastboot is, where I get it from and not to mention how to get it work, so I think this is no option for me.
Right now I have resigned. Nothing seems to work. I consider getting a new phone. But before I do this I wanna ask you one last question: can flashing the bootloader theoretically effect anything? I think my phone IS bricked at the moment, so I'm not anymore afraid of flashing the bootloader. But if it would even theoretically be impossible, that this would change anything, then it's just a waste of time. So does flashing 90.78 bootloader via RSD Lite change anything?
Thank you!
Click to expand...
Click to collapse
Why give up without trying? I believe you should flash it to see if it changes anything...How worse than this can it get?
Please...do not take my words for granted...Inform yourself from other sources before you try this...and if you do let us know if you successfully managed to get your phone back!

You misunderstood me. I wanted to try it, but if someone would have said that it's a waste of time, then I wouldn't have done it.
So I tried it, but flashing the bootloader (90.78 --> 90.78) didn't change anything. Still getting boot loops.
What do you think. Try a downgrade to 90.73? Is a downgrade even possible?

LukeTS said:
You misunderstood me. I wanted to try it, but if someone would have said that it's a waste of time, then I wouldn't have done it.
So I tried it, but flashing the bootloader (90.78 --> 90.78) didn't change anything. Still getting boot loops.
What do you think. Try a downgrade to 90.73? Is a downgrade even possible?
Click to expand...
Click to collapse
I dont think that is possible. I've read here on the forum somewhere that downgrading the bootloader is not possible...but you should search, maybe you find that it's possible.
Anyhows, I dont think your phone is lost, I just think we're missing something!

I also think it's not possible. I've read this in some forums, too.
It seems that it isn't lost. I was happy, as I found out, that I can enter recovery and bootloader. I thought it could easily be restored. But then nothing worked for me. So we must miss something, but I have no clue what.

What do you mean by:
"Then I tried to restore via Nandroid. This seemed to work well, but after a reboot I got this bootloader error again."
Are you sure you have enough battery?
You could try restoring a nandroid from other recovery. Replace the recovery from your sd-card. If you use Androidiani 3.3 try an older version of it or another OpenRecovery.

Having trouble flashing stock firmware.

Hey guys, whenever I turn on my moto G (second edition) I get spammed with applications not responding so I cannot actually do anything apart from powering off. I also cannot factory reset from fastboot as it justs fails.
So I have been trying to flash stock firmware manually but whenever I use ADB it does not pick up the device. I'm guessing this is due to USB debugging not being enabled but I canno't enable it as I cannot get to my settings. Is there anyway other way to flash stock firmware?
My bootloader is locked if that helps. (According to fastboot)

LG G4 H81120i Bootloops (Stuck at white T-Mobile Screen)

Hello.
Last night I decided I wanted to root my LG G4 running marshmallow (so we're talking about H81120i). I was able to unlock my bootloader, restart the phone and use it, etc. I was able to boot into TWRP (but not anymore for some reason) and restart the phone and use it as well, however, when I installed SuperSu using TWRP and cleared my cache my phone gets stuck at the second white t mobile screen.
I am able to get into download mode, factory reset mode, etc, just not access android. When I plug my phone into my the drivers suggest that it is a COM6 port. The LG support software recognizes my phone while in download mode though. What are my options here? Will it be safe to flash H81110n using the lg flash tool 2014 version or will that break the phone more? I thought I'd ask here first because I've always found any and all information I need for this sort of thing here.
If you need any more information to safely answer this question I will provide anything you need.
Thanks.

toxicturn said:
Hello.
Last night I decided I wanted to root my LG G4 running marshmallow (so we're talking about H81120i). I was able to unlock my bootloader, restart the phone and use it, etc. I was able to boot into TWRP (but not anymore for some reason) and restart the phone and use it as well, however, when I installed SuperSu using TWRP and cleared my cache my phone gets stuck at the second white t mobile screen.
I am able to get into download mode, factory reset mode, etc, just not access android. When I plug my phone into my the drivers suggest that it is a COM6 port. The LG support software recognizes my phone while in download mode though. What are my options here? Will it be safe to flash H81110n using the lg flash tool 2014 version or will that break the phone more? I thought I'd ask here first because I've always found any and all information I need for this sort of thing here.
If you need any more information to safely answer this question I will provide anything you need.
Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Make sure you carefully follow the guide.
Did you perhaps only boot into twrp but not install it?
I would try to flash the kdz again through either LGBridge or LGUp again as you still have download mode.

[Solved]Bricked. Can't recover stock ROM after installing TWRP 3.1.0-3. Nothing works

I have successfully unlocked the bootloader and managed to install TWRP 3.1.0-3 but that's about it. I cannot install any other TWRP version but the one I mentioned. I tried installing Magic Rainbow custom ROM but it doesn't work properly (apps are super slow, entering developer settings makes the settings app crash, can't set a password etc.). So with that I can at least access the phone interface with limited options. Developer settings crashes when I choose it; if I can get through then I can't enable USB debugging, it keeps turning itself off right as I enable it. I can't use update function so I have to use 3 button installation, which randomly fails to work very often. Due to this I haven't been able to install any updates.
I kinda gave up on rooting already, I just want to get my old firmware back at this point but I can't even do that. SRKTools stock marshmallow recovery doesn't work either. It's as if TWRP 3.1.0 has taken over everything. On the rare occasions that I managed to get EMUI update via 3 button installation it would say that the update doesn't match the current version (or something like that). I tried using recover for b378 and managed to run the 3 button update but it always gets stuck at 5%. It gives up after a while, tries booting twice and then goes into eRecovery screen. My bootloader PHONE unlocked text is in red if it matters.
I've been actively trying to fix this for the last 11 hours (yes I'm not exaggerating at all). Please, PLEASE someone help me out with this!

I've also tried using the unbrick tool of the latest SRK Tool 2.0 for b378. It goes flawless, phone restarts and does a factory wipe but then doesn't boot after the Huawei screen. It tries booting twice and then it goes into eRecovery screen. Have I ruined some hardware here?

It seems like 3 button upgrade is my salvation and it doesn't work. Many times I hold it down, I get a slightly different screen but it again hangs at booting text. I managed to flash all recovery, boot and system image files and got the installing update screen in my b378 update, but it hangs at 5%. I couldn't even manage to get the installing update screen for common b136. Also when I try to flash system.img I get an error with flashing system which is FAILED (remote:sparse flash write failure).

First at all: The Magic Rainbow custom ROM is based on B383 so it wont work on B378 firmware thats your fault here.
Just flash the rollback package (find it in my signature) and after this flash B383 or if it not work start with B136. U have to do all with the dload method.
Fast solution?
https://forum.xda-developers.com/p9/development/p9-moonlight-rom-v1-0-b378-stock-t3567223
flash the B378 version. probably your problem is solved by this.

I'm very well aware that Magic Rainbow doesn't work with b378. That's probably the reason I have those issues with it. But it's the only way I can access the phone's interface in case I need to use it for a fix.
I tried flashing b378 already multiple times, without rollback and it did not work. Is it safe to use the rollback though? My oem is c432, would it create any issues to use that? Should I flash c900 oem first or can I go with the rollback right away? I literally cannot install any stock rom without having frozen/looping bootscreen atm so I can't complete any step that requires me to do that.
I've also tried flashing b136 plenty of times already. I can't even flash the system.img. I can't flash the system of any of the b100 series.

Lauran_N said:
I'm very well aware that Magic Rainbow doesn't work with b378. That's probably the reason I have those issues with it. But it's the only way I can access the phone's interface in case I need to use it for a fix.
I tried flashing b378 already multiple times, without rollback and it did not work. Is it safe to use the rollback though? My oem is c432, would it create any issues to use that? Should I flash c900 oem first or can I go with the rollback right away? I literally cannot install any stock rom without having frozen/looping bootscreen atm so I can't complete any step that requires me to do that.
I've also tried flashing b136 plenty of times already. I can't even flash the system.img. I can't flash the system of any of the b100 series.
Click to expand...
Click to collapse
u tried the rom i mentioned?
it is safe to use the rollback package. any firmware after will retrive your oem to c432. so you dont need to flash the oem info package.
1. flash rollback package via dload (watch out to have only the UPDATE.APP file in dload folder)
2. flash B383 via dload (2 files need to be flashed!)
3. flash special SuperSU_for_EMUI5.zip
4. have fun
again if u can boot magic rom then you can flash and use Moonlight rom v1.0

xtcislove said:
u tried the rom i mentioned?
it is safe to use the rollback package. any firmware after will retrive your oem to c432. so you dont need to flash the oem info package.
1. flash rollback package via dload (watch out to have only the UPDATE.APP file in dload folder)
2. flash B383 via dload (2 files need to be flashed!)
3. flash special SuperSU_for_EMUI5.zip
4. have fun
again if u can boot magic rom then you can flash and use Moonlight rom v1.0
Click to expand...
Click to collapse
I cannot flash rollback using 3 buttons method. I see the "your device is booting now" text and then it goes to TWRP menu. Nothing happens. This is what I mean with 3 button method not working. Every single update fails probably because of this. Is there anything else I can do to flash it?
I've also tried flashing b378 and then doing the rollback. Still doesn't work: It hangs at 5% as it did with the b378 update.
Also, is there a special way of flashing those 2 files of b383? Is it just one after another? I doubt I can flash them at the same time since they have the same name.

YES IT WORKED! Thank you the rollback actually made the difference. I had to go for b136 and then upgrade manually through there with the stock OS though. And I believe rollback changed the status to LOCKED instead of RELOCKED. And I was a complete moron for I couldn't do 3 button update because my cable was still plugged in. I had a moment of epiphany when I noticed what the symbol actually represents. It was like discovering who Keyser Soze was lol. Let this idiocy stay here for there might be others like me; this way they might fix it without embarrassing themselves like I did.

Glad it worked for you.
Next time just read the threads in this forum.
There are several toturials how to flash the p9 the right way.

Lauran_N said:
YES IT WORKED! Thank you the rollback actually made the difference. I had to go for b136 and then upgrade manually through there with the stock OS though. And I believe rollback changed the status to LOCKED instead of RELOCKED. And I was a complete moron for I couldn't do 3 button update because my cable was still plugged in. I had a moment of epiphany when I noticed what the symbol actually represents. It was like discovering who Keyser Soze was lol. Let this idiocy stay here for there might be others like me; this way they might fix it without embarrassing themselves like I did.
Click to expand...
Click to collapse
Can you explain in detail how your fact? That would be nice

Genysix said:
Can you explain in detail how your fact? That would be nice
Click to expand...
Click to collapse
1. Flash Rollback Package
2. Flash Firmware Package/s
3.Unlock booloader
4.Flash twrp
5.Flash SuperSU
6.Ready
Just read the threads in this forum guys and you errors will magically dissappear or not even happen

xtcislove said:
1. Flash Rollback Package
2. Flash Firmware Package/s
3.Unlock booloader
4.Flash twrp
5.Flash SuperSU
6.Ready
Just read the threads in this forum guys and you errors will magically dissappear or not even happen
Click to expand...
Click to collapse
Every time I try to flash, with 3 buttons method, it puts me "software install failed"
I tried to flash official rom with twrp but he can't finish the process.
I tried to flash custom rom. When I want to boot, he bootloop.

Hi,
I am at a complete loss and going round in circles. My phone has bootlocker unlocked message at moment. In adb fastboot devices finds the phone, but the SRK tool fails to find it sticking on 'waiting for phone'. I tried to flasg the Huawei rollback but that fails (presumably due to being unlocked). I cannot relock via fastboot as that gives 'remote: command not allowed' error.
Update
- I have just checked fastboot - it says Phone Unlocked & FRP Unlock.
- Next I used Huawei Update Extractor to get boot, recovery, cust & system img from the "HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0_EMUI 4.1_C432B166_United Kingdom_Channel-Others" Package.
It seems I still cannot boot and device still says unlocked etc..
Update 2 :-
Copied the dload/update.app file from the HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0 zip. Managed to get it to start installing, only to get Software Install Failed msg. However reboot let me start the phone. So currently have Build No: EVA-L09C432B166 on.
At this point I just want my phone either back to initial factory state or able to flash roms, whichever is easier to get to. Any help greatly appreciated. I've been getting nowhere following guides I have found, so would really appreciate some help here.
Thank You

Genysix said:
Every time I try to flash, with 3 buttons method, it puts me "software install failed"
I tried to flash official rom with twrp but he can't finish the process.
I tried to flash custom rom. When I want to boot, he bootloop.
Click to expand...
Click to collapse
Ok first of all, using TWRP back up everything you have there (backing up SD card isn't really needed unless you plan to wipe it too). Then, using TWRP again just wipe everything but OEM and SD card (external storage). Then, create a folder called "dload" in the main SD card directory and put ONLY the update.app in it (use the stock b136 as suggested). Now you need to flash a stock recovery using bootloader again. Just use the Huawei Update Extractor and get both recovery.img and boot.img from the rom that you're using to flash (in this case b136). Put them in the same folder as adb. Run adb cmd, write commands "fastboot flash recovery recovery.img" and then "fastboot flash boot boot.img" and finally "fastboot reboot". Quickly unplug your usb cable and use the 3 button force update (Vol Up+Vol Down+Power button all held together and don't let go until you see the update start). It should work without a problem if you had managed to wipe everything using TWRP. If it still doesn't work you could try deleting OEM info as well and flashing a new one (c432) which you can find on the forums. Back up is important in case it still doesn't work, you might need them to undo things.
If it boots, it means you've learned how to do it and you can probably unbrick it as much as you want haha. You can update to Nougat (7.0) and EMUI 5 using Huawei Updater 2.0 along with HiSuite, there is a guide here on the forums to do so by updating to b182 then to b360/b361>b378>b383 which I was unable to find for now. After that you can install a custom rom without an issue. I figured I wouldn't mess with it anymore but frankly it's likely that you are just soft bricking by skipping something very simple and failing because of that unless you went ahead and did things that you are explicitly told not to do so. If you end up having it unlocked/relocked might as well try and get a custom rom really.
If the update gets stuck at 5% or you have the icon of a usb cable end with a lightning on it your mistake is that you didn't unplug it. If the update keeps failing without these it's likely that you're using the wrong firmware and you could try using another one (FULL+PV+MV ones if you're going for a higher one). Or you could try to follow the rollback and then the update as I did. if you do the rollback then the update, your phone might get a LOCKED status again (yes not relocked).
If you are missing something or you think you have a stupid question and too shy to ask it here just PM me.

Phil_UK said:
Hi,
I am at a complete loss and going round in circles. My phone has bootlocker unlocked message at moment. In adb fastboot devices finds the phone, but the SRK tool fails to find it sticking on 'waiting for phone'. I tried to flasg the Huawei rollback but that fails (presumably due to being unlocked). I cannot relock via fastboot as that gives 'remote: command not allowed' error.
Update
- I have just checked fastboot - it says Phone Unlocked & FRP Unlock.
- Next I used Huawei Update Extractor to get boot, recovery, cust & system img from the "HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0_EMUI 4.1_C432B166_United Kingdom_Channel-Others" Package.
It seems I still cannot boot and device still says unlocked etc..
Update 2 :-
Copied the dload/update.app file from the HUAWEI_P9_Firmware_EVA-L09_Andriod 6.0 zip. Managed to get it to start installing, only to get Software Install Failed msg. However reboot let me start the phone. So currently have Build No: EVA-L09C432B166 on.
At this point I just want my phone either back to initial factory state or able to flash roms, whichever is easier to get to. Any help greatly appreciated. I've been getting nowhere following guides I have found, so would really appreciate some help here.
Thank You
Click to expand...
Click to collapse
So you're saying that you're able to boot your phone on stock b166? Then update it to b182 first. I had to keep pressing the check update for a while before it popped up. I was busy at the time so I didn't mind the wait time but I bet you can do it faster forcefully, got to be a guide around here somewhere. Here is the guide to update it all the way to b383 from b182.

Lauran_N said:
So you're saying that you're able to boot your phone on stock b166? Then update it to b182 first. I had to keep pressing the check update for a while before it popped up. I was busy at the time so I didn't mind the wait time but I bet you can do it faster forcefully, got to be a guide around here somewhere. Here is the guide to update it all the way to b383 from b182.
Click to expand...
Click to collapse
I'm on B166 currently. Phone tells me it has update for B182, on reboot I get the device unlocked message and it sticks on 'Your device is booting now'.
Also tried Huawei updater....that sticks at 'Listened on Port 41279'
Thanks

Phil_UK said:
I'm on B166 currently. Phone tells me it has update for B182, on reboot I get the device unlocked message and it sticks on 'Your device is booting now'.
Also tried Huawei updater....that sticks at 'Listened on Port 41279'
Thanks
Click to expand...
Click to collapse
Getting the device unlocked message shouldn't indicate anything, only that you didn't lock it again. It might be that you didn't install your current rom correctly. You could try flashing TWRP, backing up everything and then wiping all of it f. It means you'll be romless for a while but worst case you can recover what you backed up with TWRP and then flash it with a stock rom again. There are guides to flashing everywhere and I've made my own guide here. I can't really give you advice on your situation since I haven't ever been there. I just dabble with these things, so I can't really find a solution for everything.
You are connected to HiSuite while running Huawei Updater right? It needs to be able to see your phone (usb debugging on or HDB mode) and set to usage via proxy.

Lauran_N said:
Getting the device unlocked message shouldn't indicate anything, only that you didn't lock it again. It might be that you didn't install your current rom correctly. You could try flashing TWRP, backing up everything and then wiping all of it f. It means you'll be romless for a while but worst case you can recover what you backed up with TWRP and then flash it with a stock rom again. There are guides to flashing everywhere and I've made my own guide here. I can't really give you advice on your situation since I haven't ever been there. I just dabble with these things, so I can't really find a solution for everything.
You are connected to HiSuite while running Huawei Updater right? It needs to be able to see your phone (usb debugging on or HDB mode) and set to usage via proxy.
Click to expand...
Click to collapse
Thanks for your help. Where do you set the usage to via proxy? Perhaps thats my issue.

Phil_UK said:
Thanks for your help. Where do you set the usage to via proxy? Perhaps thats my issue.
Click to expand...
Click to collapse
Run HiSuite. Make sure your phone is connected to it. Top right you'll see 4 buttons: 3 horizontal stripes, minimise, full screen and X. Press 3 stripes one and choose settings. In the first tab called General under the 4th section you'll see Proxy. Enable it and enter 127.0.0.1 for address and the given listening port as the port. Leave the username and password blank. Press apply. Then you probably have to choose the system upgrade from the main screen of HiSuite. I don't recall exactly but this is about how it goes.

Lauran_N said:
Run HiSuite. Make sure your phone is connected to it. Top right you'll see 4 buttons: 3 horizontal stripes, minimise, full screen and X. Press 3 stripes one and choose settings. In the first tab called General under the 4th section you'll see Proxy. Enable it and enter 127.0.0.1 for address and the given listening port as the port. Leave the username and password blank. Press apply. Then you probably have to choose the system upgrade from the main screen of HiSuite. I don't recall exactly but this is about how it goes.
Click to expand...
Click to collapse
Many Thanks
I managed to flash B360_update.zip via recovery instead. I also have a B360_update_data_full_hw_eu.zip but not sure what that is for.

[SOLVED] Samsung Tab 3.7.0 SM-T210 recovery and OS broken

Hi everyone,
I have retrieved a Samsung Tab 3.7.0 SM-T210. The OS was the old KitKat 4.4.2, very slow and buggy. I tried to flash a new recovery and OS and spent the 3 last days getting fails. I think I have read the all internet about this situation and would like to make a last try with your help.
When I got the tablet, I was surprised that in download mode it was indicated custom and custom binary and not official as it has not, I think, been flashed in the past by the people owning it. With HW rev 0x5 at the end.
The first thing I wanted to do was to unlock the bootloader, however, I could not find any option in developer mode talking about OEM bootloader, neither Auto Update. After reading some people on forumes saying that this device might not have a locked bootloader, I finally thought that this tablet did not have its bootloader locked. Then I decided to go further with the flash of a TWRP recovery.
At the beginning the stock recovery was working. I am under archlinux, I have fastboot and heimdall. To do it as right as possible I installed a VM with Windows 10 and tried to flash a custom TWRP corresponding to the tablet with Odin. But the process got stuck at the SetupConnection step. I installed Windows 7 too, tried 5 different Windows OS, tried 4 different USB cables, reinstalled the USB drivers, tried 5 different Odin versions, tried different archives, just recoveries and all stock system. Still getting stuck at the SetupConnection.
I finally decided to try heimdall thinking that the VM could be the problem. With heimdall I run flash commands such as heimdall flash --RECOVERY twrp-3.2.3-0-lt02ltespr.img --no-reboot and got it doing something, the shell was saying it's 100% done and the tablet, in download mode, was showing a complete blue bar. Then, the recovery was just broken. Could not access it anymore, the Samsung Tab3 logo showing up and staying when trying to access it. I tried to flash some others archives, I opened it off and remove the battery for 5 minutes, still the same thing.
The operating system was still accessible and buggy, applications saying connection issues, etc. I did a factory reset from the running KitKat android OS and now have the Samsung Tab3 logo showing up and staying when trying to access it.
Now, I can only access the download mode and that's all. I have the impression that I am not the first one having these kind of trouble with this tablet. Is it a hardware issue on all these tablets ? Should I try something more advanced with heimdall, dd ?
Does someone have a solution in this situation ?
Thanks for your time and help.

I finally used heimdall and was able to flash all the partitions with the stock images. Now I am back in stock version. I would like to flash a TWRP recovery.
Can someone tell me if I have to unlock the bootloader with this device ? If it is, how can unlock it ? I can not find anything in the settings developer section, and can not use a call number input in order to enter a system code as it's a tablet. Do I have to wipe something from the stock recovery in order to see it ?
Thanks for your time.

Hi -yo-.
You don't need to do OEM unlock as this device is so old.
Also twrp-3.2.3-0-lt02ltespr.img is NOT for this device.
For recovery look from here and for ROM here.

Thanks jonezy82 for the answer. Indeed, I figured all of that out.
I decided to get it back stock and not trying to flash anything custom.
Thanks for your time.