I rooted my Huawei y360 today. An update came to my phone from Huawei and I downloaded and installed it. The phone restarted and now is stuck in bootlog -it won't restart fully. It keeps coming up in recovery mode....... I need HELP!
shem_christoph said:
I rooted my Huawei y360 today. An update came to my phone from Huawei and I downloaded and installed it. The phone restarted and now is stuck in bootlog -it won't restart fully. It keeps coming up in recovery mode....... I need HELP!
Click to expand...
Click to collapse
I had the same thing. It looks like Huawei bricks the phone on purpose. Not very customer friendly
Here's how to unbrick :
Download a Huawei stock firmware, for instance from
http://consumer.huawei.com/nl/support/downloads/detail/index.htm?id=77123&key4=Y360&key5=webisearch
This particular version is 2016-3-25 V100R001C577B113 847.34 MB
Unzip the file and copy dload/update.zip including the directory to the root of an sd card.
Then press Vol-UP and Power at the same time, and select install updates. Done.
i have an problem my huawei y360 is giving me problem its trying to load up and stop a went to the bootlog so am trying to custom rom it because i dont have any assess to the phone.
hello.
i have the same issue here with my y360.
after i did kingroot and restarted my phone after an update only the logo boot remained.
the fw update from sd card didnt work because the phone doesn't recognize the card, afterwards i tried to flash it with the sp flash tool (old and new versions) but it was either ''invalid scatter file'' or ''dram error something...'' ofcourse i tried different fw versions but nothing worked.
anybody has an idea what to do or i should throw it to the garbage? thanks
I have the same thing going on. Trying to fix y360 for my nephew. Keeps bootlooping. It's stock.
Tried to use SP Flash Tool, but it keeps nagging about a faulty scatter.txt file, even though I downloaded the newest firmware directly from Huawei (so it has to be the right one).
I then tried to do an ADB sideload, that's what I can access right now. adb sideload update.zip (from inside the manufacturer's .rar file).
adb push does not work because ADB is not recognised, because the phone won't turn on.
Goes ok until 53% and then crashes. Internal memory runs out?
From what I can find,I should push the dload folder to sdcard, but I can't, because I can't mount the external sdcard to transfer the folder to.
So, my only option seems to be to borrow someone's phone with a microSD slot to transfer the folder, then change the card to the y360? Or get an adapter SD->microSD, then transfer the folder? Neither of which are available to me right now. Is this for real?
Damn, I miss the fastboot flash system system.img command of the more advanced phones.
70% of the instructions about this model bricking are in Spanish, so it is kind of hard to figure out what to do.
shem_christoph said:
I rooted my Huawei y360 today. An update came to my phone from Huawei and I downloaded and installed it. The phone restarted and now is stuck in bootlog -it won't restart fully. It keeps coming up in recovery mode....... I need HELP!
Click to expand...
Click to collapse
try to flash stock rom
Related
Hi everyone, I have a problem. I recently got a Huawei y220 and rooted it and enabled USB debugging, tweaked the SystemUI.apk and it all went good, I had no problem rebooting. I also changed my bootscren with BootScreen from the Play Store.
But today, my phone got stucked in bootloop, and i know why, I changed the /system/fonts permissions to 666, and also when I was trying to change the default font (DroidSans.tttf and DroidSansBold.ttf) copied a font file, so in that folder there was some permissions changed and an extra font. I had to to do something so i locked my phone. When I returned a couple of minutes later the phone was like off, so i removed the battery and rebooted it. It got stucked on my bootscreen, and didn't showed me my ADW launcher.
I can't install CWM as there is no file for this model (because it's very new), I can't flash anything as far as I know. Tried downloading the official "upgrade" from Huawei, copied the file, but I can't seem to enter the "Software Upgrade Mode", (VOL UP + VOL DOWN + POWER KEY), I press those keys for about a minute and nothing happens.
I know my phone isn't fully bricked, for now, so, how can I change those file permissions through my PC or Linux?
I can enter the bootloader screen BTW.
I also tried AromaFM, but i get a signature error.
I've already wiped/factory reset and wiped cache.
Thanks for your time!
--
TheEdwardRC
I thought the way you update / restore the stock firmware was by the update.app method? The update should be in an archive and once you unpack it should be a folder named : dload with the update.app in it. That whole folder should go on the root of the SD card so it should read /sdcard/dload. Unless it is a different y220...
Otherwise, you're kinda screwed because unless you have adb access when it is bootlooping (rare), there won't be much to do. You won't have adb in recovery either since it is still stock.
I guess it is the normal y220. The problem is that I can't get into the Software Upgrade Mode. Also, my other choice was AromaFM but i don't know how to stop it to verify the signature verification. If i could do that, i could have root acces to the files. Or maybe could install a POSSIBLE backup that i found online...
Well, when i am in recovery the device is detected on windows, but ot mounted...
Thank you
My point was, according to the info that I found, you don't update that one via the Software Update mode, you do it via the method I was talking about with the update.app in the dload folder on the SD card.
Huawei Ascend Y220 U00
After installing a theme pack, my huawei Y220 has been stuck in bootloop. I found a toolkit on some forum, it requires my device mounted on a Computer, I got all necessary drivers, but the pc could not install my device. It shows the device on device manager on the PC but after 3sec it ejects. Pls I need help.
look here, this will help you unbrick your device
http://en.club.vmall.com/forum.php?mod=viewthread&tid=13433&highlight=unbrick+huawei
Hi everyone !
first of all, sorry for my poor english.
i'd just rooted my plk-l01 using fastboot tool, and some weeks after, I did a REALLY stupid thing, after putting my simcard, i tried to install the 5.1.x update.
Of course it didn't worked. My phone just boot on twrp recovery, and a guy told me that wipe the phone would work. Bastard. Now I just have my twrp, alone.
I found this tutorial -> http://forum.xda-developers.com/hon...ers-how-to-root-update-fix-t3255452?nocache=1 (in the bootloop fixing section)
I've download the extractor and update, but I have two things that doesn't match. first, in the UPDATE.APP file, I don't have boot.img and stuff but CRC.img, CURVER.img...
And the WTF part comes when I plug my phone to my computer. It detects my phone storage (terribly empty) and my sd card, but the name of my phone is now GEM-703L, an other Huawei phone.
What can I do ?? I don't wanna touch anything without being sure I won't transform my phone onto a 299$ paperweight, and I really hope fixing is possible.
Thanks a lot for your future answers, and sorry if someone had the same trouble, but I didn't find anything which could help me on XDA.
Idiocrate said:
And the WTF part comes when I plug my phone to my computer. It detects my phone storage (terribly empty) and my sd card, but the name of my phone is now GEM-703L, an other Huawei phone.
Click to expand...
Click to collapse
That's the mediapad X2, it's what the Chinese TWRP is actually for...
Go [here] to grab the stock recovery of your choice (B100 or B120)
Go [here] and download B100 or B120 FULL
Unzip and copy the UPDATE.APP to your sdcard in directory called "dload"
Flash stock recovery
Turn phone on holding power, vol+ and vol-
Wait until finished.....
Relax :silly:
I was running CM12 and everything was fine. I received a notification to update to CM 13 and I selected yes. It installed OK, but no GAPPS. I tried everything I could think of to install GAPPS, and kept getting errors. IN my frustrated efforts, something happened to my TWRP and now I only have CM Recovery. I'm trying to reinstall TWRP but my phone is being recognized as a "Marshall London Bootloader Interface" ONLY when in the Fastboot and Recovery mode. I have Huawei Hisuite installed and it recognizes the phone fine when powered on, but as soon as I boot into Fastboot and Rescue mode, it reverts to the MLB interface. I am at my wits end as to how to get my PC to recognize my phone properly when in Fastboot and recovery. I did try removing and reinstalling drivers when in Fastboot, but the Marshall Interface keeps on getting inserted. Any suggestions?????? (I also seem to have erased the SD card that has my original system backup files on it. I tried to flash several downloaded stock ROMs using CM recovery, but they all error out. )
I was finally able to re load TWRP using the Huawei Hi Suite. I flashed Carbon ROM and GAPPS and everything seems to be OK but I still cannot use ADB because the phone is recognized by Windows as a Marshall device ONLY when in bootloader mode and ADB does not find the device. When I connect normally it is recognized as a Mate 2 and it connects normally to Hi Suite. I have no idea what could be wrong, but I have read of other people who have this mysterious "Marshall" device show only up when in bootloader mode. Anyone have any ideas????? Can I go back to stock from here if I don't have a saved recovery image to see if I can fix this???
I have no idea what Marshall device means. Is it possible to place the stock 5.1 ROM on a blank micro SD card and follow the flashing instructions? (boot to download mode or whatever it's called)
ScoobSTi said:
I have no idea what Marshall device means. Is it possible to place the stock 5.1 ROM on a blank micro SD card and follow the flashing instructions? (boot to download mode or whatever it's called)
Click to expand...
Click to collapse
I explained what "Marshall Device" is in the first post. I ended up going back to stock (322) and loosing root. I then updated to 5.1 using the SD card. Everything seems to be working OK. Maybe I'll root again and start over when I have more time.
Hello everyone.
So I decided to update my device as i find out that there is a new default ROM available for my device that is Infocus m530.
I downloaded the ROM and i was flashing it through Software Update Tool (SUT) in Normal mode. The installation process got stuck at 16% for like 10 or 15 minutes so I removed the USB (I know its a dumb move ) . And I rebooted the device and got stuck into a boot loop.
I can access the default 3e recovery mode only but because my ROM was in format ob .nb0 I am not able to Flash it using stock recovery, I can no longer access the FastBoot mode,
When i try to boot the device up it goes into One or two loops and the a windows pop up saying no command. In that window if I press power button the stock recovery shows up.
I tried to flash the ROM again using SUT in emergency mode but the device is getting disconnected automatically. In device manager its showing up as Mediatek Pre Loader USB VCOM for a second or 2 and then automatically getting disconnected and then same No Command menu.
For a minute a new device is also popping in the Explorer which usually contains all the default driver of the phone.
Any way I can recover my Bricked Device
Any help or advice would be much appreciated.
Hi , try to flash this firmware from normal Recovery , once you download rename to update now put firmware inside empty formatted sd card and put inside your phone to start flashing from recovery .
https://www.kriztekblog.com/2016/06...=o67JcQ2b1GjkodlJa9ULilWJwoqb1xZxq6CkVi5D960=
I didn't checked it is for zip or for flash tool so test it first . Good luck .
FIXED
Teddy Lo said:
Hi , try to flash this firmware from normal Recovery , once you download rename to update now put firmware inside empty formatted sd card and put inside your phone to start flashing from recovery .
I didn't checked it is for zip or for flash tool so test it first . Good luck .
Click to expand...
Click to collapse
I already tried it but it didnt work.
So finally I was able to fix the device. The META Mode ain't a myth. Flashed the ROM correctly in META mode and the device booted up properly.
Hi there! I'm hoping someone on XDA Developers can help me sort out a root gone-wrong.
I did my best to follow the guide on XDA. I have an Umidigi A9 Pro with 6gb ram. I was successfully able to get the android tools on PC and was able to unlock the bootloader. I went to the Umidigi website to get the ROM. I think I *might* have grabbed the wrong one. Once I got this zip from the Umidigi website, I unzipped the folder and copied the boot.img that was in that root folder to the device. I then went into Magisk and patched the img. I then copied the patched img to my PC then use the commands on the XDA guide to flash the image to the device, the flash was successful (I think). However the device is now stuck in a boot loop. The device displays the Umidigi OEM logo and the android logo; underneath it says in small text:
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
after 5 seconds the screen goes black and then comes back with the same screen. This happens continuously. I have tried holding the volume down, the power button, and several combinations of volume up, down, and power. Holding all buttons down makes the screen stay black, however while plugged into the PC the PC still makes the device connected and disconnected sounds off and on. Whenever I release the buttons, it goes right back to the loop. Windows PC plays the device connected and disconnected sound on and off. The command prompt is not able to affect the device. When I run "adb devices" it doesn't display the phone so it doesn't seem that windows is detecting the device.
ROM: https://community.umidigi.com/forum.php?mod=viewthread&tid=22236&extra=page=1
https://www.umidigi.com/page-Download.html
I'm hoping for some help on this one
Thank you!
It should be obvious that when being in a bootloop ADB cannot function: On Android side the ADB daemon gets started and after seconds closed, and this over and over again.
In the simplest explanation, a bootloop describes when your phone is stuck in a loop of rebooting. The term "bootloop" is just a more common way of saying "reboot loop."
Curious if you ever managed to get this figured out? I'm in essentially the same situation, though I was not attempting to flash a ROM. I successfully managed to get TWRP 3.5.2 installed and then I was trying to get Magisk installed.
My phone data was wiped, which honestly I didn't care about, however I must have done something wrong with the Magisk installation as now I have the rebooting issue.
I'm able to use ADB and have been trying to push a ROM to the sdcard folder of the internal storage. ADB says the file has successfully completed, but nothing is on the phone. I fixed the issue of the storage showing up as 0MB by changing from EX4 to EX2 and then changed it back to 4.
Really unsure of how to flash a ROM if I can't get the file to pushed to the phones internal memory though.
Zeidwinder said:
Curious if you ever managed to get this figured out? I'm in essentially the same situation, though I was not attempting to flash a ROM. I successfully managed to get TWRP 3.5.2 installed and then I was trying to get Magisk installed.
My phone data was wiped, which honestly I didn't care about, however I must have done something wrong with the Magisk installation as now I have the rebooting issue.
I'm able to use ADB and have been trying to push a ROM to the sdcard folder of the internal storage. ADB says the file has successfully completed, but nothing is on the phone. I fixed the issue of the storage showing up as 0MB by changing from EX4 to EX2 and then changed it back to 4.
Really unsure of how to flash a ROM if I can't get the file to pushed to the phones internal memory though.
Click to expand...
Click to collapse
I honestly haven't messed with it since. It was a very cheap extra android phone I had laying around. Once it got messed up I pretty much just put it in a drawer and said "maybe another day"