Hi,
I bought a cheap A95x China tv boxes. I was editing build.prop to get leanback launcher and android TV features.
I was trying to flash stock ROM but it always failed and the box ended up bricked. So I took working box and made a TWRP backup.
Then I restored this backup on bricked one. I was able to boot again but only with SD card inserted.
This box should boot when you plug it to power, but nothing happens when I connect it. Inserting microSD card will trigger the boot.
Any suggestions what might go wrong? I was also trying to flash TWRP but it didn't help
Can reflashing boot.img help? I couldn't find suchn img
You can find the files you need here...
ErikHric said:
Hi,
I bought a cheap A95x China tv boxes. I was editing build.prop to get leanback launcher and android TV features.
I was trying to flash stock ROM but it always failed and the box ended up bricked. So I took working box and made a TWRP backup.
Then I restored this backup on bricked one. I was able to boot again but only with SD card inserted.
This box should boot when you plug it to power, but nothing happens when I connect it. Inserting microSD card will trigger the boot.
Any suggestions what might go wrong? I was also trying to flash TWRP but it didn't help
Can reflashing boot.img help? I couldn't find suchn img
Click to expand...
Click to collapse
Friz's Nexbox File Repository:
https:// mega.nz/ #F!F9xjTSSa!R0vJfTC2U6Qc2skNMrr1iQ[/url]
Related
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
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.
Previously, I had this phone rooted, and running CM12 with an open source gapps setup, with no problems. I also had TWRP installed, and an SD card with a copy of my ROM as I liked it, and my data.
Everything worked, and I was able to update my Android version and expand functionality quite a bit, which was useful while traveling abroad.
The other day however, when seconds before I had been using it as my hotspot, I tripped over the charging cord and dropped the phone quite hard on tile.
It broke into pieces, with the back coming off and the battery coming out.. The display is fine. I thought I killed it entirely, but I took the battery out and left it alone for half a day, and when I came home, I realized that it would:
1. Charge
2. Boot to recovery
3. Boot to download
This gave me some hope.
However, doing anything else would result in a bootloop.
I booted into recovery in preparation to re-flash my rom, and TWRP was not able to mount my SD card, and would not recognize my data there.
Additionally, when I tried to wipe everything but my SD card, TWRP failed to mount all partitions, as if something got corrupted.
When I tried to repair or change the file system type, this too failed. I cannot seem to get TWRP to recognize any storage. It says the phone is empty, with no internal, no external, and no OS.
Just a bunch of red "failed" lines every time I try to do something through the recovery.
I checked my SD card externally using an adapter on my mac, to make sure it was not corrupted. All my data is still there, including the backup of my ROM. However, since the phone will not recognize it, it's useless, and I can't find an Odin flashable .tar version of the CM12 ROM for this phone, plus when I tried to convert a copy to the correct file type, it failed to flash.
I tried to flash a copy of the stock rom (metroPCS version) to begin with, that I had saved on my computer.... which worked before when I messed up my initial flash. This time, It will flash successfully per Odin, but cause a bootloop.
Odin will still recognize my device... but adb from my mac terminal will not recognize it when I have the device connected or I would try to rebuild the file system that way.
I feel like I am going in circles and running out of options, or missing something..(possibly several things) but... I don't want to give up on this phone just yet, even if I had to demote it from daily driver use in the end ... any advice would be appreciated.... Thank you sooooo much!
Edited to add: I got ADB to recognize the device and ran a restore command, based on a file I had locally. This is what happened:
localhost:~ user$ adb restore ~/Downloads/cm-12-20150319-UNOFFICIAL-gardalte.zip
Now unlock your device and confirm the restore operation.
/sbin/sh: /sbin/bu: not found
Also adb remount resulted in a failed output.
Lastly, it appears abd only works in terms of recognizing my device when I am in recovery.
Hi guys, trying to fix a colleagues t95z, when you boot up, it goes through the t95z logo then the loader screen then just black screen
I've tried to pin hole and update rom
tried a-a usb cable pc can't detect
I mananged to put twrp 3.0.2.0 on but basically useless i think, when i click reboot into recovery it says "no Os"
any ideas? its the 2gb/16gb version
conqug said:
Hi guys, trying to fix a colleagues t95z, when you boot up, it goes through the t95z logo then the loader screen then just black screen
I've tried to pin hole and update rom
tried a-a usb cable pc can't detect
I mananged to put twrp 3.0.2.0 on but basically useless i think, when i click reboot into recovery it says "no Os"
any ideas? its the 2gb/16gb version
Click to expand...
Click to collapse
Why don't you just install the stock firmware via USB stick or TWRP?
https://forum.freaktab.com/forum/tv...o-2gb-16gb-scv1-final-rom?p=634945#post634945
Post #335
The ROM is for the T95z+. No idea if it's compatible with the T95z
I can't get into recovery mode to flash. I'm stuck on t95z plus screen. Can't access twrp anymore either.?
conqug said:
I can't get into recovery mode to flash. I'm stuck on t95z plus screen. Can't access twrp anymore either.?
Click to expand...
Click to collapse
So how did you manage to flash twrp and is it the correct version for the device?
i managed to install this
https://forum.xda-developers.com/an...ecovery-twrp-3-0-2-sunvell-t95z-plus-t3557812
was able to see twrp a couple times couldn't do much, went to reboot clicked recovery popped up at top saying "no OS" then rebooted and its sat on t95z plus boot logo since, can't get back to twrp or any recovery
conqug said:
i managed to install this
https://forum.xda-developers.com/an...ecovery-twrp-3-0-2-sunvell-t95z-plus-t3557812
Click to expand...
Click to collapse
That is what led me to build my own in the link I gave you, it added support for image backup and flashing.
If twrp is giving the 'No OS' message it means that you've wiped the system partition.
If you indeed have the T95 plus and running MM then flashing the image I posted should fix it.
However I'm a little confused as to why you can't boot to twrp as this not affected in any way by having no OS installed. Irrespective of whether it's stuck on the T95z plus screen you should still be able to hard boot to recovery.
Have you tried to see if ADB is active at this point?
Hi
How do I see if adb active?
I've tried USB a to a with no detection. I don't know if box gets a network connection
I will try flashing with that rom again with a different USB or sd card
If I try pin hole method on boot box goes to t95z + screen flickers to a grey then goes to t95z logo again
conqug said:
If I try pin hole method on boot box goes to t95z + screen flickers to a grey then goes to t95z logo again
Click to expand...
Click to collapse
Is adb working?
Hi need to try Monday. Left my cable at work
How do I know if adb work?
conqug said:
Hi need to try Monday. Left my cable at work
How do I know if adb work?
Click to expand...
Click to collapse
Boot the phone then plug the cable in then at a command prompt where you have the adb binary stored type the following:
adb devices
You should get some sort of confirmation with a serial number.
ashyx said:
Boot the phone then plug the cable in then at a command prompt where you have the adb binary stored type the following:
adb devices
You should get some sort of confirmation with a serial number.
Click to expand...
Click to collapse
hi no can't get any connection to adb, just says list device attached and nothing there
tried to install twrp again but logo just flickers screen goes grey then logo appears again T95z plus
conqug said:
tried to install twrp again but logo just flickers screen goes grey then logo appears again T95z plus
Click to expand...
Click to collapse
How are you installing twrp?
If you can still install twrp then why not install the firmware from USB?
just via sdcard and pin hole method.
I can try via usb do i need to pin hole ?
do i just add SUPERCELERON_V1_FINAL_TWRP_SYSTEM_IMAGE to a usb or do i unzip? or use burn card maker etc
conqug said:
just via sdcard and pin hole method.
I can try via usb do i need to pin hole ?
do i just add SUPERCELERON_V1_FINAL_TWRP_SYSTEM_IMAGE to a usb or do i unzip? or use burn card maker etc
Click to expand...
Click to collapse
I suggest reading this thread and using these tools.
https://forum.xda-developers.com/an...ers/amlogic/opensource-amlogic-tools-t3786991
hi i've tried all of these tools but no joy
box sitting currently saying "boot" and logo on screen but nothing else..
think its unsaveable ( atleast by me )
conqug said:
hi i've tried all of these tools but no joy
box sitting currently saying "boot" and logo on screen but nothing else..
think its unsaveable ( atleast by me )
Click to expand...
Click to collapse
What actually happened to this box?
I'm led to believe that twrp installed. And he clicked wipe all etc and it deleted everything including os
I've tried 2 different USB cables to try get connection
conqug said:
I'm led to believe that twrp installed. And he clicked wipe all etc and it deleted everything including os
I've tried 2 different USB cables to try get connection
Click to expand...
Click to collapse
If that's the case then the device should be savable as its only a software issue.
If you can boot to twrp then it should be a relatively simple fix, so should using the USB stick method.
Are you actually installing twrp or just attempting to boot it from the sd card?
My box is on Magendanz's Nexus ATV rom. but thats 6.0 and I wanted to try 7.1 or 8.0 but it refuses to let me update any way I try.
I have tried the USB Flashing tool and ATVxperience rom but my box isn't being recognised as being in "burnable" state - the reset pin does work but its not recognising or putting into correct state for the USB tool to see it
I have tried Burn Card maker and ATVxperience rom but again it isn't recognising card or the "burnable" state
I have tried TWRP but my TWRP didnt allow me to flash the IMG saying "Size of image is larger than target device" - I think Magendanz's rom maybe didnt have all the right partitions or sizes? He's not responding to support requests
I tried to get original FW back using TWRP but same issues.
Tried to put a new TWRP on and buggered that up so now box thinks it has no recovery to boot to. BOX DOES BOOT and I can access terminal and root but when I tried dd if=/storage/recovery.img of=/dev/block/recovery it wrote a new TWRP but "reboot recovery" just gets me the Nexus logo.
I'd be tearing hair out if I had any left. I am guessing the partitions all need rebuilding and TWRP reinstalling but no ideas left.... Any help???