Related
Hello everybody,
I would kindly ask someone for assistance how to repair the Amlogic 8726-MX based TV box which is stuck on the boot.
Origin of the problem starts when I rushed to change DPI settings with one application from Play Store and failed to boot after restart. Boot was stuck at endless loop of Android logo with vertical yellow bars due to wrong DPI/ resolution settings. After I tried to make the reset of the system (Safe mode through button reset) and which failed, I tried to prepare and boot from SD Card with some ROMs I found online for very similar model with same chipset, and I am stuck at brand (Corto) logo after the Amlogic logo is displayed. I can not enter recovery mode when following instructions. This model has dedicated reset button, so the "toothpick" method is not needed here. However holding it 5-10 seconds during the boot, does not start the recovery in my case, so I am not sure if:
a) Recovery is damaged?
b) I didn't prepare the SD card in correct way? (I used DD + u_boot.bin)
c) My SD card does not contain correct version of files so it does not start recovery?
I assume I would need to identify the exact model of the board, quite similar to generic 8726-MX player, but board layout is little bit different. Product is sold under brand Corto, model AMPC-200, and it seems to be the same as model CM-Q7 by Coltech Cynmate. Production date is September of 2013. On board there is sign B6_V1.1. Images attached.
I am even considering to buy second unit, if it would be possible to extract recovery from new unit and fix the old one.
I would be thankful if anyone could suggest some solution.
Thanks!
do you resolved the situation
Pleas help
Hello everyone,
I bought Smart TV Stick http://goo.gl/b9ivdd
And i have problems with WiFi.
Device see a lot of AP, but can't connect with my router at all. I'll tryed to changed encryption (WEP/ WPA/ WPA2) and nothing changes. My router is wrt54gh. Maybe devices can't connect cos this router have only G standart?
Any ideas?
Thank you, best regards
Bump. I am also interested. I have the same device, but mine works properly. However I would like to know how to access basic recovery, and install TWRP or CWM recoveries.
mitramix said:
Hello everybody,
I would kindly ask someone for assistance how to repair the Amlogic 8726-MX based TV box which is stuck on the boot.
Origin of the problem starts when I rushed to change DPI settings with one application from Play Store and failed to boot after restart. Boot was stuck at endless loop of Android logo with vertical yellow bars due to wrong DPI/ resolution settings. After I tried to make the reset of the system (Safe mode through button reset) and which failed, I tried to prepare and boot from SD Card with some ROMs I found online for very similar model with same chipset, and I am stuck at brand (Corto) logo after the Amlogic logo is displayed. I can not enter recovery mode when following instructions. This model has dedicated reset button, so the "toothpick" method is not needed here. However holding it 5-10 seconds during the boot, does not start the recovery in my case, so I am not sure if:
a) Recovery is damaged?
b) I didn't prepare the SD card in correct way? (I used DD + u_boot.bin)
c) My SD card does not contain correct version of files so it does not start recovery?
I assume I would need to identify the exact model of the board, quite similar to generic 8726-MX player, but board layout is little bit different. Product is sold under brand Corto, model AMPC-200, and it seems to be the same as model CM-Q7 by Coltech Cynmate. Production date is September of 2013. On board there is sign B6_V1.1. Images attached.
I am even considering to buy second unit, if it would be possible to extract recovery from new unit and fix the old one.
I would be thankful if anyone could suggest some solution.
Thanks!
Click to expand...
Click to collapse
You need to go to the freaktab site, find the device, download the gbox midnight rom, sd flash tool. Use the tool on pc to flash the sd, put the sd in the box, keep the reset button pressed, its accessed via the rear of the device with maybe a cocktail stick if you dont know, then connect power keeping the reset pressed till recovery appears. Apply update on sd card, reboot. Everything you need for this box, roms, how to s etc, even cwm are on freaktab. The gbox rom, flashed correctly fixes bricked devices. Mine included. Hope this helps, it should do.
Sent from my LG-P875 using XDA Forums Pro.
Anlogic 8726 mx v1.1 image
t, I have Amlogic 8726 mx v1.1 tv box that has become stuck on the android logo after I attempted to install an update for the MX2 thinking it was the same thing, how wrong I was. Does anyone still have the V1.1 image available, every link to the V1.1 image have all been taken down.
Thanks in advance
Hey all,
So I bought a cheap 9" tablet off eBay for use as an electronic billboard outside my dorm room door (cool, huh?)
I've been trying to root it for a long time so I could disable the touch screen/buttons on the device. I don't want people powering it off or something weird. I tried a bunch of different rooting methods to no prevail and eventually decided to try installing a custom recovery image using fast boot. Well, I definitely screwed something up as now the tablet just keeps rebooting as shown in the gif below.
[Gif video] i.imgur.com/ZtU4RtG.gifv
The screen will turn on and off and it seems to do it too quickly to be recognized by fast boot.
Should I paint a target on the back and practice my aim or is there any hope here?
Thank you for reading.
I figured it out! For anyone who has a problem in the future, I'll tell you how I did it.
Get PhoenixCard, it allows you to reinstall firmware through a micro sd card.
blogtechtips.com/2015/11/24/phoenixcard/
Then, get the iRulu firmware from the iRulu website. I checked the sticker on the back of my tablet and my model is like an x1924 (first part of whatever that code is.) I downloaded the "X1921 X1922 X1931 X1932 Firmware_YHK" firmware as it was the closest one. There should be instructions on how to use the PhoenixCard software to reinstall your firmware, but I found that I had to remove the card and try burning again if it failed to burn. It'll say "error" at the end if it failed.
Then I tried plugging in the card and booting the tablet a couple of times until a loading bar appeared on the screen. Wait patiently, and eventually it will turn off again. Remove the card and boot up and you're good!
my tablet
hey my model number says x9 and i am kinda confused because i cant find the firmware for it. itsvthe same 9" 4.4 will that firmware work on mine
Jason1077 said:
hey my model number says x9 and i am kinda confused because i cant find the firmware for it. itsvthe same 9" 4.4 will that firmware work on mine
Click to expand...
Click to collapse
I also have an IRULU x9 (boot screen says expro x1) I have a serial # jx944wf1507061e. I found the firmware on the Irulu site as firmware for JX944 & JX945 HERE
xx.irulu.com/download/lists.html
replace xx with www
I rooted my tablet but it is stuck in factory reset boot loop. If there is a power cycle i lose all programs installed and the tablet goes back to factory settings out of the box state. However, I still have root and superuser (Kingoroot) installed.
I will try flashing it with phoenixcard and with the factory firmware and post if it fixed it.
***update** Flashed the firmware with Phoenixcard, used JX944 firmware and it is back to factory specs working as it did when it was stock.
Thanks to you both. I'm going to try this over New Year's. Wish me luck!
Sent from my Nexus 5 using Tapatalk
This will help you unbrick a bricked FireTV 2. You must download the following:
FireTV 2 Recovery Installer
FireTV 2 Recovery
Unbrick Images (md5sum: 5e774497b3bad5c47d1c744410f6db12)
Extract all 3 zip files to the same directory.
You must decide if you want to use unbrick.img or unbrick+ramdisk.img. Using unbrick.img, it should take about 30 minutes. Using unbrick+ramdisk.img it could take up to 2 hours. You can only use unbrick.img if you have an sdcard. If you have an sdcard, place ramdisk-recovery.cpio.lzma in the root directory of it.
Run unbrick_firetv2.bat for Windows or unbrick_firetv2.sh for Linux or OSX.
First, it will ask you which file you want to use, unbrick.img or unbrick+ramdisk.img. You must type the name of the image you want to use.
Make sure the USB cable is connected and turn on the FireTV 2.
Then it will start reading from the FireTV. Then it will prompt you with a warning:
Code:
No target file specified. Is this a partition image?
If this is not, DO NOT CONTINUE, otherwise press 'y' to continue.
Write partition image? <y|n>
Type a 'y' and hit enter.
It should start writing. Eventually it will finish. If you put the ramdisk on the sdcard, make sure it is plugged in and power cycle the Fire TV. It should skip the bootmenu and take you straight to recovery. If for some reason the USB keyboard doesn't work, unplug and replug it. It should start working.
rbox said:
This will help you unbrick a bricked FireTV 2. You must download the following:
FireTV 2 Recovery Installer
FireTV 2 Recovery
Unbrick Images
Extract all 3 zip files to the same directory.
You must decide if you want to use unbrick.img or unbrick+recovery.img. Using unbrick.img, it should take about 30 minutes. Using unbrick+recovery.img it could take up to 2 hours. You can only use unbrick.img if you have an sdcard. If you have an sdcard, place ramdisk-recovery.cpio.lzma in the root directory of it.
Run unbrick_firetv2.bat for Windows or unbrick_firetv2.sh for Linux or OSX.
First, it will ask you which file you want to use, unbrick.img or unbrick+recovery.img. You must type the name of the image you want to use.
Make sure the USB cable is connected and turn on the FireTV 2.
Then it will start reading from the FireTV. Then it will prompt you with a warning:
Code:
No target file specified. Is this a partition image?
If this is not, DO NOT CONTINUE, otherwise press 'y' to continue.
Write partition image? <y|n>
Type a 'y' and hit enter.
It should start writing. Eventually it will finish. If you put the ramdisk on the sdcard, make sure it is plugged in and power cycle the Fire TV. It should skip the bootmenu and take you straight to recovery. If for some reason the USB keyboard doesn't work, unplug and replug it. It should start working.
Click to expand...
Click to collapse
Awesome rbox! I see you've been busy...Really appreciate everything you do for us Fire TV folks.
Awesome work as always!
Thank you mate... Your great work made my day and got out of bricked state !!!!!
Got to recovery and flashed your rooted 5.0.31 and rebooted to perfectly working aftv2 + rooted .. Good job as always mate , thanks
One question, could I just flash the rooted 5.0.4 from recovery or should I do something else??
samykoka said:
Thank you mate... Your great work made my day and got out of bricked state !!!!!
Got to recovery and flashed your rooted 5.0.31 and rebooted to perfectly working aftv2 + rooted .. Good job as always mate , thanks
One question, could I just flash the rooted 5.0.4 from recovery or should I do something else??
Click to expand...
Click to collapse
You can flash whatever version you want...
rbox, looks like amazon sent me a bricked fire tv, while im at possession, i figured a i play around with it.
when i got it it was stuck to amazon white amazon logo,
so i waited for it for like 30 minutes to boot, but nothing changes... then with recent root method (aftv gen 2)
i figured i install this
http://forum.xda-developers.com/fire-tv/development/firetv-2-recovery-t3309780/page17#post65265240
i was able get to recovery!
and applied pre rooted firmware, but after completion,
i think its beyond bricked..
no screen, my led flash drive does not even flash or blink anymore when i put it on boot...
i can still handshake still apply the unbrick method
my question is after applying this brick.img
would i suppose to get a screen? and boot up
but still the same no screen nothing... not even white amazon logo...
or this is done..
thanks
daffung said:
rbox, looks like amazon sent me a bricked fire tv, while im at possession, i figured a i play around with it.
when i got it it was stuck to amazon white amazon logo,
so i waited for it for like 30 minutes to boot, but nothing changes... then with recent root method (aftv gen 2)
i figured i install this
http://forum.xda-developers.com/fire-tv/development/firetv-2-recovery-t3309780/page17#post65265240
i was able get to recovery!
and applied pre rooted firmware, but after completion,
i think its beyond bricked..
no screen, my led flash drive does not even flash or blink anymore when i put it on boot...
i can still handshake still apply the unbrick method
my question is after applying this brick.img
would i suppose to get a screen? and boot up
but still the same no screen nothing... not even white amazon logo...
or this is done..
thanks
Click to expand...
Click to collapse
After using unbrick.img, if you put the ramdisk on the sdcard, you should get recovery. If not, then there is something bad the hardware.
Many thanks, rbox -- unbrick_firetv2.bat worked for me in bootcamp. Selected unbrick+ramdisk.img, then rebooted into TWRP. Initially when I installed prerooted 5.0.5_r2, setup gave me a screen (after remote pairing and language selection) that it was checking for updates. The setup then halted with an error window that it could not connect to Amazon's server, and that I should power off and reset the AFTV. I then flashed prerooted 5.0.4_r2, completed the initial setup, and reflashed prerooted 5.0.5_r2 (which let me get around the update error).
Again, thanks for all your work!!
rbox said:
After using unbrick.img, if you put the ramdisk on the sdcard, you should get recovery. If not, then there is something bad the hardware.
Click to expand...
Click to collapse
i wonder what caused that bricked.. , ( well it was already bricked, when amazon send it to me it was stuck at white amazon logo, then only when i applied the pre rooted firmware, thats when it stop showing screens from there..wouldn't it fix the problem already since i was able to get to recovery.....
id try the sd card 1 last thing il probably go to walmart and try that, if nothing fix it i guess its total beyond brick..
Hi,
thank you very much for your great work @rbox!
Just a note:
I think, in the bash script, there is a "2" in the last line that doesn't belong there?
And there is a "unbrick+ramdisk.img" file, but no "unbrick+recovery.img" in the zip container. Some might get confused by that...
But everything works fine (using ramdisk)!
thx
Takeoo111111 said:
Hi,
thank you very much for your great work @rbox!
Just a note:
I think, in the bash script, there is a "2" in the last line that doesn't belong there?
And there is a "unbrick+ramdisk.img" file, but no "unbrick+recovery.img" in the zip container. Some might get confused by that...
But everything works fine (using ramdisk)!
thx
Click to expand...
Click to collapse
Thanks. I fixed it all.
rbox said:
After using unbrick.img, if you put the ramdisk on the sdcard, you should get recovery. If not, then there is something bad the hardware.
Click to expand...
Click to collapse
rbox, looks like its a hardware problem? but problem is i had white screen when i applied the pre rooted fire tv, thats when i get no screen, no boot... do think its possible a fix for this, via handshake?
daffung said:
rbox, looks like its a hardware problem? but problem is i had white screen when i applied the pre rooted fire tv, thats when i get no screen, no boot... do think its possible a fix for this, via handshake?
Click to expand...
Click to collapse
Well try the unbrick image and see if it works.
rbox said:
After using unbrick.img, if you put the ramdisk on the sdcard, you should get recovery. If not, then there is something bad the hardware.
Click to expand...
Click to collapse
rbox said:
Well try the unbrick image and see if it works.
Click to expand...
Click to collapse
yup,
sucessfully flashed unbrick.img, and had sd card ramdisk-recovery.cpio.lzm.
still the same...
no boot, no screen, not even white screen?
and no signal from hdmi
I am afraid I have to report a brick on 5.0.5r3 -
Played some Vice City, went back into Kodi, played a video that was still in the paused state, then the screen flashed to black and then back to the Video in Kodi twice and then - a dreaded blackscreen.
Upon a reboot I still get the amazon logo, I get the recovery bootscreen and also can still enter TWRP recovery, but when I try to boot into the normal OS I only get the amazon logo and then a fade to black (amazon Fire TV animated logo not showing up). The blue LED on the Fire TV is steadily blinking along...
(Switched TVs and HDMI cables - just in case (no HDCP problem.. ))
Already wiped /system /data /data including media /cache and /dalvik - and reinstalled both 5.0.5r1 and r3 multiple times.
Right now I have two questions - 1st (for the fast ones, because I am trying it anyway) - should I still try to unbrick using this tutorial (i.e. If I have access to the recovery and already formated the whole range of partitions once - does the unbrick image do anything more than that?).
And 2nd - is there any "factory image" maybe without the stock recovery disabled - just in case, at this point - I'd try most things - really...
harlekinrains said:
I am afraid I have to report a brick on 5.0.5r3 -
Played some Vice City, went back into Kodi, played a video that was still in the paused state, then the screen flashed to black twice and then - a dreaded blackscreen.
Upon a reboot I still get the amazon logo, I get the recovery bootscreen and also can still enter TWRP recovery, but when I try to boot into the normal OS I only get the amazon logo and then a fade to black (amazon Fire TV animated logo not showing up). The blue LED on the Fire TV is steadily blinking along...
(Switched TVs and HDMI cables - just in case (no HDCP problem.. ))
Already wiped /system /data /data including media /cache and /dalvik - and reinstalled both 5.0.5r1 and r3 multiple times.
Right now I have two questions - 1st (for the fast ones, because I am trying it anyway) - should I still try to unbrick using this tutorial (i.e. If I have access to the recovery and already formated the whole range of partitions once - does the unbrick image do anything more than that?).
And 2nd - is there any "factory image" maybe without the stock recovery disabled - just in case, at this point - I'd try most things - really...
Click to expand...
Click to collapse
The unbrick image just puts enough on system to be able to get to recovery. If you can already get to recovery, it won't get you anything. The disabled stock recovery isn't going to effect anything while running android. All it does it prevent the bootloader from running it. I can't really explain it if you did an advanced wipe of data.
Hardware Issue probably. Thanks for the fast response.
Cheers.
(I'll do another advanced wipe - just for kicks.. )
edit: Went through with another full wipe - rebooting the device afterwards (= softbrick for sure, because not even TWRP is accessible and there is no OS on the device) - which at that point got "parked" on the white amazon logo indefinitely. (Perfect for the "I aint know nothing" returning the device approach. Just in case Amazons 5.0.5 turns out to brick a few more Fire TVs... As long as rbox didnt modify the kernel, I'd say its Amazons fault. ) Then went through the unbrick procedure in this thread - which worked as described (TWRP was installed on the device and autobooted on the powercycle after the unbrick script had finished). Then installed 5.0.5r1 again and rebootet - just to be met with the same error profile as before "dark screen" - not even the animated amazon logo (just the white one in the beginning).
This time - on a better TV screen it was visible though, that the screen showed a small horizontal line, and then flashed in a lighter black color twice, before going back to full TV black. So yes the problem seems to lay somewhere on the video signal path. Its curious though, that TWRP still got (and gets) displayed...
Works perfect. Thx
Can someone help me? I followed all the steps in the guide and when the unbricking program is writing the filesystem, it always gets stuck at 17%. Maybe I am doing something wrong?
rbox said:
After using unbrick.img, if you put the ramdisk on the sdcard, you should get recovery. If not, then there is something bad the hardware.
Click to expand...
Click to collapse
I am in a boot loop. Goes to amazon white logo. Light on FireTV2 turns orange then reboots into custom recovery but it automatically starts trying to mount partitions (one of them is cache) and it fails on all of them. Then moves along to the white amazon screen again and repeats the entire process. I ran the unbrick.img and the problem persists.
I'm currently in the process of running unbrick+recovery.img method to see if it makes any difference. Should it? Is there anything that I may be overlooking?
I'm fairly sure that the reason this happened is from checking ALL the check boxes in the format/wipe section of the custom recovery. After that these issues happened. Does that mean permabrick?
Hello guys,
I am really in need of help. For reason that does not matter any more I have tried to root my phone and now it is unable to start. I followed the steps listed in the below tutorial:
bbs.elephone.hk/thread-9919-1-1.html
However after following some steps, video tutorials and further confusions I ended up trying to "Firmaware Upgrade" my phone with SPFlash Tool, but unfortunately the process was ended prematurely and my phone is not able to start at all (black screen and no reaction from any button). I understand that everyone must take responsibility for the consequences followed by rooting a phone, but I wanted to ask you guys if I am able to recover the phone or I would need to buy a new one.
Here is more detailed information of what I tried and what is the problem I am experiencing:
- Error that I see when I try to "Format & Download" (or any other option / action that SPFlash tool has):
BROOM ERROR : STATUS_PRELOADER_INVALID (-1073545212)
[HINT]:
- What I tried:
1. Reinstalling the drivers because I tought that they are incorrect. Every downloaded dirver results to the same error and I believe that the issue is not related to the dirvers at all (I use Windows 7 Ultimate with the SP_Driver_v2.0).
2. Tried using different versions for SPFlash Tool, but it appears that only the latest ones works with the scatter file that I have (MT6755_Android_scatter.txt). Versions that I tried are - v5.1552; v5.1524; v5.1620; and after trying evrything I believe that the issue is not related to the used tool nor scatter file.
My conclusion is that somewhere along the way I re-formatted my phone, but since the processes ended prematurely this may have disrupted the correct format of the internal storage.
Is is possible to recover from this and if it is what steps / actions should I take to do so. I would really appreciated some help of you guys and will be glad if the phone is working back (promise to stop being a "hacker").
Best Regards,
A fellow that need helps or a new phone
I just wanted to add that I was able to recover my phone. YEY!!!!
For those of your who ran to the same problem here is what I did to restore the phone from the boot loop:
1. Remove the battery - this is quite a tricky part, but if you follow the steps and be careful there should not be any problems:
- Remove the back from the phone - since it is no meant to be easily removed you could use a plastic card and start from the top of the phone (where the ear jack is located).
- After that you would need to remove the top plastic cover - it is placed to protect the main board and all modules. You would need a small "Philips" screwdriver in order to remove all screws. Note that there is one hidden screw that is placed on the middle bottom part of the plastic cover. You could recognize it by the elephone logo placed on top of it.
- Once the plastic cover is removed you will see the connector of the battery. Remove so that the device is actually turned off.
2. Download a STOCK ROM for your device:
- The STOCK ROM for Elephone P9000Lite was downloaded from here:
4pda.ru/forum/index.php?showtopic=697579&st=20#entry47838700
All required images along with the scatter.txt file should present inside the downloaded archive.
3. Flash the ROM by using SPFlash tool:
- What I did here is to follow a tutorial that is specifically for hard bricked devices:
devs-lab.com/how-to-unbrick-mediatek-device.html
In my case I had to use the Format + Download option in SPFlash tool and select all images to be flashed. The important part was that the phone's battery had to be disconnected, all images selected by clicking the "Format + Download" option and finally hit the "Download" button. Once this is done you can connect the battery again and connect the device to your computer.
After the process is completed the device can be powered on and it should start booting.
I hope that I can help someone with these steps and that you do not give up on your phone.
Best Regards,
Happy fellow that resurrected his pone
I've bricked my other devices before and all i had to do to fix it, was remove the battery and format & download the original software. As you meantioned, with P9000 (same as with the Lite version), the problem is non-removable back cover and battery. Thank you for this tutorial, but it'd be better is somebody make a video tutorial or just add any media at all as many people might not want to do it, because of fear to break something under the back cover
Thanks for this, I am currently in the same position you were. I've cracked open the phone and am just trying to work out which connector feeds the power from the battery. I was pretty sure my problem was repairable so wasn't too stressed, but I hadn't thought to attempt to open the phone up like you did. It was surprisingly easy, and I don't think I'll have done any permanent damage. I'm hoping I can get the phone going again without any data loss, I was trying to flash recovery when I bricked it so hopefully I simply flash TWRP and she boots again.
awedxz said:
I just wanted to add that I was able to recover my phone. YEY!!!!
For those of your who ran to the same problem here is what I did to restore the phone from the boot loop:
1. Remove the battery - this is quite a tricky part, but if you follow the steps and be careful there should not be any problems:
- Remove the back from the phone - since it is no meant to be easily removed you could use a plastic card and start from the top of the phone (where the ear jack is located).
- After that you would need to remove the top plastic cover - it is placed to protect the main board and all modules. You would need a small "Philips" screwdriver in order to remove all screws. Note that there is one hidden screw that is placed on the middle bottom part of the plastic cover. You could recognize it by the elephone logo placed on top of it.
- Once the plastic cover is removed you will see the connector of the battery. Remove so that the device is actually turned off.
2. Download a STOCK ROM for your device:
- The STOCK ROM for Elephone P9000Lite was downloaded from here:
4pda.ru/forum/index.php?showtopic=697579&st=20#entry47838700
All required images along with the scatter.txt file should present inside the downloaded archive.
3. Flash the ROM by using SPFlash tool:
- What I did here is to follow a tutorial that is specifically for hard bricked devices:
devs-lab.com/how-to-unbrick-mediatek-device.html
In my case I had to use the Format + Download option in SPFlash tool and select all images to be flashed. The important part was that the phone's battery had to be disconnected, all images selected by clicking the "Format + Download" option and finally hit the "Download" button. Once this is done you can connect the battery again and connect the device to your computer.
After the process is completed the device can be powered on and it should start booting.
I hope that I can help someone with these steps and that you do not give up on your phone.
Best Regards,
Happy fellow that resurrected his pone
Click to expand...
Click to collapse
Hello all. I softbricked my phone while attempting to flash TWRP, and ended up with a phone that wouldn't present anything on screen. So I've located an old XP computer to rule out any driver issues, and using the battery removal mentioned above I was able to flash the factory 20160422 firmware which is what I believe my phone had before I started tinkering. I unticked the userdata box as I flashed it, and left the recovery box ticked which I thought would fix any corrupt recovery that my tinkering caused. The flash took some time, but I got the green tick indicating that it went well. However I still get nothing on screen, the only time I get anything is when I plug it into charge, I get a green battery charge icon for a few seconds before it fades away. If I leave it plugged in for a while, the screens starts to faintly flash sporadically. Does anyone have any advise for me? @awedxz, could you please confirm that the battery connection is on the far left, a shiny copper ribbon with a small silver rectangle plug that clicks into the board?
jiddahidda said:
Hello all. I softbricked my phone while attempting to flash TWRP, and ended up with a phone that wouldn't present anything on screen. So I've located an old XP computer to rule out any driver issues, and using the battery removal mentioned above I was able to flash the factory 20160422 firmware which is what I believe my phone had before I started tinkering. I unticked the userdata box as I flashed it, and left the recovery box ticked which I thought would fix any corrupt recovery that my tinkering caused. The flash took some time, but I got the green tick indicating that it went well. However I still get nothing on screen, the only time I get anything is when I plug it into charge, I get a green battery charge icon for a few seconds before it fades away. If I leave it plugged in for a while, the screens starts to faintly flash sporadically. Does anyone have any advise for me? @awedxz, could you please confirm that the battery connection is on the far left, a shiny copper ribbon with a small silver rectangle plug that clicks into the board?
Click to expand...
Click to collapse
Let it to charge more time
Thanks mate, this advise was spot on. It must have had 0% battery after fixing it! It's now alive and charging up. How neat that Mediatek devices can be unbricked so easily, although I'll have to be a bit more careful in future I think! My previous devices have been Motorola, HTC and Samsung devices, each with different tools and flashing techniques. Haven't bricked any of them in the past, but it's nice knowing this device will be hard to permanently brick.
chtsarts said:
Let it to charge more time
Click to expand...
Click to collapse
Had the same problem, a small cable that goes from the power button was disconnected. Connect the cable and it should run just fine
Just to chime in, I soft bricked my phone as well.
I managed to get it back to life, without taking the phone apart, so that is not a necessity.
Here's what happened: I had CM13 installed on the phone and wanted to go back to stock, so I flashed it according to the guides, also overwriting the preloader.
After that, the phone was dead, as in unable to turn on, no charger detection etc.
As is already known, this phone has an "emergency" line / device, that will turn on once you connect it to the computer and press the VOL+ button (the device will show up for a couple seconds in the Windows device manager).
So what I tried was to flash it again and again, to no avail; sp_flashtool reported the following error after trying to flash the preloader: "BROM ERROR - STATUS_EXT_RAM_EXCEPTION (-1073414139)"
Finally I tried different stock roms, from the Elephone forum.
The one that did the trick for me was the 20160304 - I loaded the scatter file into sp_flash tool and only flashed the preloader. After that, Windows suddenly recognized the phone as the preloader device, the screen turned on showing the charging image and the notification led lit up. I was able to flash the phone without errors again.
After that I flashed the rest of the stock firmware - without the preloader.
I then let the phone charge a little bit and it turned back on.
If that version of the preloader does not do the trick for you, try different ones.
No need to take the phone apart.
Good luck everyone!
For everyone's else information having this problem. I also bricked my P9000 whilst flashing TWRP and getting the RAM error. I tried every options possible but the only one that worked was to disconnect the battery. It is actually a very easy process as described as above. The battery connector is the small connector nearest to the volume buttons with the bronze coloured connector cable. It simply lifts up and your battery is disconnect. I changed the settings in SP FLASH to without battery and my phone flashed without any problems. Before this, it had been dead for over a week and all other methods failed to wake it up. Hope this helps.
---------- Post added at 11:36 AM ---------- Previous post was at 11:07 AM ----------
This video may help also
https://www.youtube.com/watch?v=irDOXh1QoKE
Hi everyone! I had the same problem (bricked phone not recognised by flash tool ecc ecc) and disconnecting the battery did the trick, but I may have messed up with some
The screen connectors and now the screen lits up but stays black. Sounds and touch screen work (I can unlock the screen because I hear the unlock sound), but the screen stays black... If I have damaged the connector (I think it's the one on the upper left, the thinner one that doesn't really click when inserted) there is not much to do, but I just wanted to know If anyone had the same issue and eventually resolved it.
Anyone have any idea on how to at least somewhat revive this thing? Tried flashing a retail ROM to this but it went a bit sour so I attempted to bring it back to stock by flashing back the stock demo ROM dump I made prior using SP Flash Tool's Write Memory feature. And it now refuses to budge at all (i.e. no screen activity, apart from the red battery indicator) as I couldn't get it to cooperate with SPFT - tried pressing volume up or down to force USB serial mode, but that didn't work either; it's just stuck at Preloader mode. I previously bricked a LeapFrog Epic before (which used the same MT8127 chip as this device), and reviving it fell through no thanks to the fact that I didn't have a backup of its security keys, but for the SE I was able to do the necessary precautions prior to flashing, it's that Write Memory killed it somehow, and I am at a loss as to how to bring this back to life. Am I SOL or is this still recoverable?
EDIT: NVM, turns out that converting ROM_0 into a scattered format and editing the scatter file for SPFT to load all images, and flashing it using SPFT v5.1532 did the trick for me. Glad I was able to make a backup this time around unlike what happened with the LeapFrog.
Anyone, pretty please??
blakegriplingph said:
Anyone have any idea on how to at least somewhat revive this thing? Tried flashing a retail ROM to this but it went a bit sour so I attempted to bring it back to stock by flashing back the stock demo ROM dump I made prior using SP Flash Tool's Write Memory feature. And it now refuses to budge at all (i.e. no screen activity, apart from the red battery indicator) as I couldn't get it to cooperate with SPFT - tried pressing volume up or down to force USB serial mode, but that didn't work either; it's just stuck at Preloader mode. I previously bricked a LeapFrog Epic before (which used the same MT8127 chip as this device), and reviving it fell through no thanks to the fact that I didn't have a backup of its security keys, but for the SE I was able to do the necessary precautions prior to flashing, it's that Write Memory killed it somehow, and I am at a loss as to how to bring this back to life. Am I SOL or is this still recoverable?
EDIT: NVM, turns out that converting ROM_0 into a scattered format and editing the scatter file for SPFT to load all images, and flashing it using SPFT v5.1532 did the trick for me. Glad I was able to make a backup this time around unlike what happened with the LeapFrog.
Click to expand...
Click to collapse
hi ! i have the same problem as you and i was wondering if i could fix stuff on my end ?
thank you in advance !
[I flashed the Nabi SE stock ROM and ended up with a black screen, unresponsive but was able to go into download mode with battery indicator.
The stock ROM flash was successful, but still didn’t turn on.]
(edited message to shorten down reply)
zaysxtun said:
hi ! i have the same problem as you and i was wondering if i could fix stuff on my end ?
thank you in advance !
[I flashed the Nabi SE stock ROM and ended up with a black screen, unresponsive but was able to go into download mode with battery indicator.
The stock ROM flash was successful, but still didn’t turn on.]
Click to expand...
Click to collapse
By battery indicator you mean the red LED light?
And did you perform a full ROM_0 backup first?
blakegriplingph said:
By battery indicator you mean the red LED light?
And did you perform a full ROM_0 backup first?
Click to expand...
Click to collapse
yup ! and i didn't make my own backup for this. i used your shared backup in one of your threads !
[ https://forum.xda-developers.com/t/nabi-mtk-root-magisk-recovery-nabi-se-discussion-thread.3770816/ ]
it worked for me in the past due to poorly unlocking the bootloader.
(bump) so my Nabi SE can enter download mode. but SP Flash Tool refuses to flash with the error code : 2004 DA_DOWNLOAD_FAIL.
on other days, it would actually flash on download mode. result = black screen on Nabi SE with RED battery indicator.
Is there a way I can fix the 2004 error?
(SP Flash Tool v5.1532)
(bump, sorry for spam)
so i have finally managed to flash everything back :’) only thing is that… the Nabi is still unresponsive (red battery indicator only red, black screen)
i heard its “stuck in download mode”.
is there a fix ?
I think it might have been hosed then, as you forgot to back up the NVRAM and all that.