Related
My stock Nexus 6 wanted to update to April security update. (I believe my phone storage was almost full)
It failed the update, is stuck on No Command dead android guy and then pops this address up.
g.co/abh
Factory reset the only option?
You might want to try flashing the update manually, using ADB and Fastboot. Doing so will wipe your device, so if you have anything in the internal storage, back it up if you can.
I try flashing manually via adb/nexus toolkit and it just says error code 7 on the phone. The device is bootlocked.
this may help
http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660
Are you trying to update with an OTA? If I remember correctly, error 7 means an OTA update check found that your phone isn't stock. This happens if you have messed with the system (rooting and other stuff), have a custom recovery (TWRP) or a custom kernel.
If the above applies to you, use factory images and fastboot to update instead (leave out userdata.img so as not to wipe your data). Ooops. Just saw you're bootloader is locked. Your data will get wiped when you unlock... Make sure to have a backup.
I have no backup, the phone is under warranty and as this has happened before. Stock update killed phone, i'm taking it to vodafone today.
I can't be bothered to mess about when my contract comes with warranty
Good thinking...
Didgeridoohan said:
Are you trying to update with an OTA? If I remember correctly, error 7 means an OTA update check found that your phone isn't stock. This happens if you have messed with the system (rooting and other stuff), have a custom recovery (TWRP) or a custom kernel.
If the above applies to you, use factory images and fastboot to update instead (leave out userdata.img so as not to wipe your data). Ooops. Just saw you're bootloader is locked. Your data will get wiped when you unlock... Make sure to have a backup.
Click to expand...
Click to collapse
Exactly same problem, struggling for a day now.
unable to unlock bootloader for flashing the device
"fastboot flashing unlock" returns OKAY but the screen still shows "Device is LOCKED. Status Code: 2"
any suggestions??
Try "fastboot oem unlock".
Strephon Alkhalikoi said:
Try "fastboot oem unlock".
Click to expand...
Click to collapse
"fastboot oem unlock" gives:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.001s
But of course I can't do that as I cannot get it to start. I tried "adb sideload image-shamu-mmb29x.zip" too, but it fails for signature verification probably because it shows I have "MMB29V" on the phone. Downloading "MMB29V" image now, will try that too.
With your bootloader locked, you cannot flash factory images using fastboot, and ADB is not for flashing factory images. You have to flash the Android N preview as an OTA in recovery to restore your device to an operable state. Once Android N finishes optimizing apps and is booted, you need to go into the hidden Development Options menu in Settings and tick "Enable OEM Unlock". Then you can unlock the bootloader in fastboot with the command " fastboot oem unlock" so you can flash factory images.
Aston Martin said:
My stock Nexus 6 wanted to update to April security update. (I believe my phone storage was almost full)
It failed the update, is stuck on No Command dead android guy and then pops this address up.
g.co/abh
Factory reset the only option?
Click to expand...
Click to collapse
Got into the same situation yesterday. Seems like it was not just a security update (it didn't say so though), but it was update for the Android-N preview.
Wasted a whole day trying to figure out what did I do to brick my phone. In the end it was just the stupid update by google.
The solution to the problem now is to update your phone to Android-N preview OTA update - you can get it from here: http://developer.android.com/preview/download-ota.html
aHR0cDovL2RldmVsb3Blci5hbmRyb2lkLmNvbS9wcmV2aWV3L2Rvd25sb2FkLW90YS5odG1s --> base64decode this to get the link [new users not allowed to put direct links ]
Steps for solving your problem:
Connect your phone to the computer
On your phone go to the No Command screen and press the three buttobns (Vol-UP + Vol-DOWN + POWER) simultaneously [it will take a couple of tries before you succeed]
You will now reach the Android Recovery screen
Select the option "Apply update through ADB"
From the computer execute "adb sideload <OTA_UPDATE_FILE_NAME>.zip"
Wait for a few minutes and you will see the update progress on adb
Here OTA_UPDATE_FILE_NAME.zip is the name of the ota-update file you download from the developer.android.com link [given above as base64]. For Nexus 6 it is - shamu-ota-npc91k-201dd8d1.zip
Hope it will save someone a lot of their important time.
Well, I am having the same issue as OP. Stock Android on Nexus 6 (t-mobile), received OTA security patch last night. Checked that I have a little over 1GB storage left (24.90GB out of 25.98GB available) and proceeded with installation. Now it says "device is corrupt" and after the four rotating colorful circle animation it gives me the "Unfortunately, Settings has stopped" message box over and over again which I cannot get past. I tried safe mode and it hits the same error.
I am trying the manual OTA update now as ravikumr posted, but I suspect it may run out of storage space since the zip file is 855MBs. Any way I can go in and clean up some space before the installation?
If the reason the original OTA update failed was due to insufficient storage, that would be a really stupid way to annoy the user. I have been reasonably happy with my phone so far but this experience today sucks. I depend on the phone for a lot of things so I never tried to root it or modify in any way, but I guess that's still not enough to make the phone reliable.
I will post my results with the manual update.
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Target: google/shamu/shamu:N/NPC91K/2751853:user/release-keys
Patching system image unconditionally...
Verifying the updated system image...
E:unknown command [retry_update]
system partition has unexpected contents after OTA update
E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
Anyone has suggestion I can try?
I couldn't wait since I needed the phone to work so I did factory reset. I had to do it twice since the first time it looked hung formatting /data (I waited over an hour) but second time it went through fairly quickly. Afterwards it was stuck on the google logo at boot, probably due to the bad system. I reinstalled the Android N preview OTA patch and it successfully completed this time, and I was off setting up the phone again.
I am still not convinced that what I have experienced was not a simple mistake that whoever put this package together forgot to put in code to check for available storage space before allowing the installation to proceed, or it could be a bug that when space ran out the installation code didn't handle it gracefully and started to do bad things. Either way it was a bad experience for me. Luckily I saved all my pictures and videos a week ago so only lost a few pictures plus other data.
I was experiencing this problem with a Nexus 6 - Update failed due to insufficient space, and it was impossible to get back into Settings to unlock the bootloader, to be able to use the Nexus toolkit or to otherwise flash a factory image.
Forgive any repetition herein, I am simply explaining how I was able to fix everything.
I am explaining how to fix this on a Windows PC. Sorry Mac/Linux users.
Firstly - if your bootloader is locked - the simplest way to get the phone back up and running is to download the Android N OTA.zip - download that here: http://developer.android.com/preview/download-ota.html
You will need to have the android sdk toolkit installed - or the basic adb/fastboot version. Click here if you need a guide on how to do that - http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Once you have got the OTA update, and adb is installed do the following:
1. Move the OTA update into the android sdk folder.
2. Rename it Update - for simplicity's sake.
4. Reboot your phone into Recovery mode (switch phone off, hold Volume Down and Power until you get to the Bootloader Menu, Use volume down to navigate to "Recovery" and then press Power. You'll see a dead looking android dude - hold Power and press and release volume up. You'll now be in stock Recovery)
5. Scroll down to Apply update through ADB and select.
6. On your PC - in the Android SDK folder, hold down Shift and then Right Click. Select "Open Command Window Here".
7. Type the following command - "adb sideload <OTA_UPDATE_FILE_NAME>.zip" and press Enter. As explained above, to make this easier I renamed the .zip as "update". It is still a .zip file, so make sure you type adb sideload update.zip.
8. You'll see the progress and once it has done, reboot the phone.
9. If you want to stick with Android N - enjoy your phone.
10. If you don't - do this. You cannot select unlock OEM from Developer options as it is grayed out. Instead (and you need to have signed into your device with a gmail address, and selected yes to be part of the Android Beta Programme) go to the following web address - https://www.google.com/android/beta?u=0
Sign in with the same google account you signed into your device with. Select enrol device. Now select de enrol device - you should then receive a notification for a system update that will downgrade your device to the latest publicly available, stable, Marshmallow build.
And thats it.
I hope this has been helpful, apologies for any repetition.
Thanks
Kam_El said:
I was experiencing this problem with a Nexus 6 - Update failed due to insufficient space, and it was impossible to get back into Settings to unlock the bootloader, to be able to use the Nexus toolkit or to otherwise flash a factory image.
Forgive any repetition herein, I am simply explaining how I was able to fix everything.
I am explaining how to fix this on a Windows PC. Sorry Mac/Linux users.
Firstly - if your bootloader is locked - the simplest way to get the phone back up and running is to download the Android N OTA.zip - download that here: http://developer.android.com/preview/download-ota.html
You will need to have the android sdk toolkit installed - or the basic adb/fastboot version. Click here if you need a guide on how to do that - http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Once you have got the OTA update, and adb is installed do the following:
1. Move the OTA update into the android sdk folder.
2. Rename it Update - for simplicity's sake.
4. Reboot your phone into Recovery mode (switch phone off, hold Volume Down and Power until you get to the Bootloader Menu, Use volume down to navigate to "Recovery" and then press Power. You'll see a dead looking android dude - hold Power and press and release volume up. You'll now be in stock Recovery)
5. Scroll down to Apply update through ADB and select.
6. On your PC - in the Android SDK folder, hold down Shift and then Right Click. Select "Open Command Window Here".
7. Type the following command - "adb sideload <OTA_UPDATE_FILE_NAME>.zip" and press Enter. As explained above, to make this easier I renamed the .zip as "update". It is still a .zip file, so make sure you type adb sideload update.zip.
8. You'll see the progress and once it has done, reboot the phone.
9. If you want to stick with Android N - enjoy your phone.
10. If you don't - do this. You cannot select unlock OEM from Developer options as it is grayed out. Instead (and you need to have signed into your device with a gmail address, and selected yes to be part of the Android Beta Programme) go to the following web address - https://www.google.com/android/beta?u=0
Sign in with the same google account you signed into your device with. Select enrol device. Now select de enrol device - you should then receive a notification for a system update that will downgrade your device to the latest publicly available, stable, Marshmallow build.
And thats it.
I hope this has been helpful, apologies for any repetition.
Thanks
Click to expand...
Click to collapse
This works if you are completely stock with no custom recovery and your OS is gone ? When your phone gets downgraded, does the OEM unlock appear in developer options so you can toggle it ? If so there are a lot of phones in all the threads that have been RMA due to this.
mikeprius said:
This works if you are completely stock with no custom recovery and your OS is gone ? When your phone gets downgraded, does the OEM unlock appear in developer options so you can toggle it ? If so there are a lot of phones in all the threads that have been RMA due to this.
Click to expand...
Click to collapse
This worked for me, specifically with the update issue on a fully stock and OEM locked Nexus 6 that became buggy after the update was attempted but there was not enough memory. After the update failed and it booted back up (there was an error your device is corrupt message on bootup) there were a ton of error messages and the settings app was broken. Package installer was also broken and Google play and media services were broken, therefore couldn't use the Wugfresh Nexus toolkit, couldn't use fastboot as OEM was locked and couldn't access settings to change it. Factory reset from stock recovery did not fix the errors and following bootup the startup wizard couldn't start either.
The only option was to sideload the OTA - however, for the Nexus 6, after the OTA installed the OEM unlock option was transparent and set at off (because my bootloader was always locked). I then enrolled the device on the Beta programme, and then unenrolled it. Almost immediately a downgrade able OTA notification arrived which dropped it back down to Marshmallow. After bootup all seemed fine, then play services stopped working. I was worried until I recieved a notification for a Marshmallow update - after that was installed everything worked fine as normal. The OEM unlock option was again available (although I decided to keep it locked).
For other devices it won't work, as I believe the Android N OTA is for a select few Nexus devices and possibly GPE devices (full list available on the website above).
Whether this work if you've completely deleted the OS - again I'm not sure. But I cannot see the harm in trying in that scenario. More experienced users could assist here. It should work as long as you can get into stock recovery.
Hope this helps.
Thanks Kam_El for posting the instructions. I followed the exact same steps except that "adb sideload update.zip" command wasn't successful (see my posts above). It only worked after I did a factory reset. My phone was stock Android with latest patches.
I followed your last step to downgrade the Android N back to Marshmallow. The main issue I have with N is that wechat crashes the system as soon as it's launched and only a reboot can fix it.
lyuanrich said:
Thanks Kam_El for posting the instructions. I followed the exact same steps except that "adb sideload update.zip" command wasn't successful (see my posts above). It only worked after I did a factory reset. My phone was stock Android with latest patches.
I followed your last step to downgrade the Android N back to Marshmallow. The main issue I have with N is that wechat crashes the system as soon as it's launched and only a reboot can fix it.
Click to expand...
Click to collapse
Glad to have helped. I had already attempted a factory reset before momentarily losing hope lol. Incidentally I'm now running N on my Nexus 9 - loving the new notifications.
Anyway ✌?
Hello developers,
pls help me to Get ride of this
I got this while Updating automatically from settings....which i got update notification
i tried to Flash stock/factory image, due to Unallow OEM unlock, i cudnt go further
Fone is LOCKED,STOCK ROM,NOT EVEN ROOTED, DEVELOPER OPTIONS OFF
i tried to update Android N via ADB SIDELOAD..............its not even detecting the zip file
it says... " Loading ..zip file " and get stuck PC
after few min, " installation aborted" displays in fone
i donno what to do .......pls help me
any way to solve this
thanks
If you can still get into recovery, download the latest OTA zip from Google's developer page, copy it to your internal storage, and flash it using the recovery. It will wipe your device storage, but at least your device will function again.
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.
Hello everyone, it's my first time writing here, but I’ve tried everything, searched everywhere, and am desperate for help.
I screwed up big time while trying to flash a custom rom on my nem-l21, as I successfully did before with my xiaomi... So what I did:
I managed to unlock bootloader with dc unlocker. Then I got stucked flashing twrp with adb tools. Everything was looking to be fine, no error messages, “flashing successful”… But, I was never able to boot into flashed twrp. Always got stuck on “your phone has been unlocked blah blah. Your device is booting.” It never booted, not in twrp, nor in stock recovery. I tried different versions of twrp from different sources, always same result (flashing successful, booting into recovery not). Booting into the system was fine. And then I made that horrible mistake. Oh, how I wish I didn’t!!
I read on some website, that you are supposed to flash the twrp as boot.img, not as recovery.img. Seemed illogical and stupid to me, but in the end I tried it. Of course, this just bricked my phone, with no possibility to boot. After hours of googling, installing, trying and crying, I managed in the end to flash back stock boot.img. But at that time, I didn’t know my build number (b359), and I flashed boot.img b351. So now I have a phone which boots into the system b359 with boot.img b351, but with lot of errors.
- developer options, security options, display and factory reset option doesn’t work and just crashes. Therefore I am not able to flash the correct boot.img b359 or anything else at all from pc, no way to enable usb debugging and oem unlocking. Adb devices → nothing. I am able to use fastboot (fastboot devices sees the phone), but when try to flash something, I get error “command not allowed”. Also I can’t enable unknown sources installation, which bothers me a lot. And I can’t make factory reset to restore the crashing settings. Also I can’t change display timeout, and original 30 secs is super annoying.
- I am not able to uninstall even apps installed by me, always just restarts system UI and app stays.
What I tried so far:
- flashing correct boot.img from pc, not working because of dev options crashing
- go into recovery, but stock one is overwritten with unfunctioning twrp, always just get stuck on “your phone was unlocked blah blah… your device is booting now”, but it never does, have to hard reboot
- go into huawei erecovery, which is working, but when I try to resolve problem from there, always ends up with errors and crashes
- connect to pc and use HiSuite, system recovery tool here always says “no problem detected”
- updating to b361 through system update settings, always crashes on 5% and sends phone into “your phone was unlocked blah blah… your device is booting now” error
- downloading the proper b359 as and update.app file, put it in dload internal storage → same error during update, put it in dload sdcard → same error, no matter which way I use to start the update
- boot into twrp or stock recovery.img through fastboot without actually flashing it, anyway error “command not allowed”
- do factory reset or update through dial codes (i.e. *#*#123456#*#* …), nothing worked
My pc is windows 10, all drivers up to date. Using powershell as an admin. Am an idiot for not making backup of the phone before I started...
So, now I have more or less functioning phone, but I can’t uninstall any apps at all, can’t install from unknown sources, can’t do nothing from pc, can’t make any update, and lot of important settings keep crashing.
I can use the phone like this, but if somebody could think about some solution for this ****ed up situation I got myself into, I would be grateful to him/her for the rest of my life.
Sorry for a long post.
Thank you in advance and have a nice day
I think using Hisuit will help. Enter Fastboot and connect ur phone to ur computer and use system recovery toll
Hi Guys,
My phone suddenly stuck at this screen since may :
Android Recovery
Xiaomi/jasmine/jasmine_sprout
9/PKQ1.180904.001/V10.0.9.0.PDIMIXM
user/release-keys
Use volume up/down and power.
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data store on this device.
- Try again
- Factory data reset
If i press try again, sometime it will go to fastboot screen.
I can go into recovery mode here but i not sure which step i should do next.
Reboot system nowreboot to bootloader
apply update from ADB
apply update from sd CARD
wipe data/factory reset
Mount/sstem
view recovery logs
run graphics test
run locale test
power off
I'm not a very tech savvy person, i would really appreciate some help as i have data inside my phone which i need. So if possible i would like to retain the data.
I tried like EDL,fastboot,and flashing none seem to work. Of course I may be doing it wrong.
Can anyone guide me step by step I be happy to give an reward via paypal.
I'm so sorry bro.... 80% of times this means you lost your data.
Is the bootloader unlocked?
blazessdd said:
I'm so sorry bro.... 80% of times this means you lost your data.
Is the bootloader unlocked?
Click to expand...
Click to collapse
Thank you so much for replying.
Nope, but I can do EDL to unlock bootloader, I already disassemble the device a few times.
Just that every time I try to flash it , it give me some error. like Bluetooth error or the version error .
Which I watch thousand of video to work but it's doesn't help. Or maybe I just watched the wrong video
Ok tell me exactly what are you doing and where you have downloaded the rom.
If it's corrupted and you try to flash it you will lose the data... Was debug USB activated on developer settings?
My device died too. After the October update, he never came back. It is looped on the home screen written "Android One".
I've tried several tutorials, it accesses the FastBoot screen, but when trying to use MI Flash appears a Bluetooth error and does not proceed.
I've tried using the adb flashing unlock_critical command, but it fails too.
He didn't have the bootloader unlocked, I now have a large paperweight.:crying:
epilifio said:
My device died too. After the October update, he never came back. It is looped on the home screen written "Android One".
I've tried several tutorials, it accesses the FastBoot screen, but when trying to use MI Flash appears a Bluetooth error and does not proceed.
I've tried using the adb flashing unlock_critical command, but it fails too.
He didn't have the bootloader unlocked, I now have a large paperweight.:crying:
Click to expand...
Click to collapse
You can try to short the edl points so you can flash the ROM again
blazessdd said:
You can try to short the edl points so you can flash the ROM again
Click to expand...
Click to collapse
I already made this attempt, "adb reboot edl" reports the message "error: '(null)' not found
Xiaomi never again