Related
Hi
When I turn on my phone all it shows is red, green, blue and white stripes across the screen with the following text:
ROSE100
SPL-1.54.0000
MicroP-Rose (LED) v10
MicroP-Rose (key) v5
PCBID 0x80
RID 0x0
At the bottom of the screen it also says "Serial", but displays no actual serial. Please see attached pic.
Please help guys. Problem initially started when phone collected dew on cold morning (camping).
Thanks!!!
You seem to be in the "flash screen".. I did that on my phone by accident, pressing power and one of the volume buttons.. Try pulling the battery out, put it back and see if it starts normally.
I have the exact same problem. Mine happened all of a sudden for no reason after turning my phone off and trying to turn it back on. Please post if you find a solution
Well, you can try to reflash your ROM. Many official ROMs can be found here.
Hi, I got the roms, but where can I read how to put the new one on my phone using my computer?
Ok, I got it I just run the .exe file to update my rom. However, there is just one problem, it says you should connect activesync to your phone. How tf do I connect activesync as my phone does not load any OS?! I tried without activesync but it doesnt work - it freezes on 0% update and after a while it runs some kind of recovery steps. So how do I get pass the activesync thing? Thanks
You can't upgrade ROM via activesync if u don't have acces to windows mobile, you can do it only from SD card.
Here http://www.megaupload.com/?d=M7OEOF2N (pass: xda) you find a Rose service manual and at the page 45 you find "ROM Image upgrade thru SD card" ...it's not complicated, read carrefuly.
Ok I read it but when I press the power button for the second time it says "No image file". I renamed the file to RoseIMG.NBH. What am I doing wrong?
I don't know what are you doing wrong ...try to rename the file to "ROSEIMG.nbh". Where did you download the ROM? ...I recomend you to put the same ROM you have on device because you don't have installed HardSPL (and I don't know if you can install it from SD card). Here http://forum.xda-developers.com/showthread.php?t=599520 are the officials roms for S740.
PS: I never tried this method on S740, I do it once on tytn II and works perfectly.
Here is how I got it to work:
Left it in the boot mode with the colorful screen until the battery is decharged enough, then tried to put it on again and it automatically turns off. So I put the USB cable in it and walla it started loading the battery and it turned on automatically and loaded WM. However, I still can not flush my ROM even through activesync.. but I am glad I can use it again.
something many forget with this fault, and I have seen quite a few is it is often not a rom issue but a hardware problem... in this case it may be a faulty up volume button, or maybe the plastic cap has shifted keeping the button held down, does the button still click ok?
The monet was a swine for the camera button giving up the ghost and doing nothing but dropping to boot loader......
Hi all,
Yesterday I was playing Angry Birds (in Android), when screen turned black and my HD2 started to make a buzzing noise. I took the battery out, and since then my won't boot. When I turn on my phone I only get the white HTC bootscreen, wich is white/black striped, and it doesn't boot any further. I included a photo of the boot screen.
I already tried multiple hard resets, no effect .
Ouch.......
Can you get to bootloader.......?
(hold vol down while turning it on)
If so, is that black n white striped too??
take the sd card out too, the one evening i tried android it all went bad and i had to hard reset, and it refused to work with the sd in.
I tried hard reset without sd card a couple of times, but nothing changed.
Bootloader works, without stripes. I already tried to flash the stock rom. I put the stock nbh file, renamed to LEOIMG.nbh, on a FAT-32 formatted sd-card, but when I started the phone in bootloader (vol down+power), the "loading" screen dissapeared as quick as it showed up and the phone got back in bootloader mode (4 color screen)..
valkjuh said:
the "loading" screen dissapeared as quick as it showed up and the phone got back in bootloader mode (4 color screen)..
Click to expand...
Click to collapse
that usually means a mistake with teh card size, formatting, nbh file or something.
I tried 2 different sd cards now, 1gb and 4gb, both did the same.
I'm going to sleep now, i'll try some custom ROM nbh-files tomorrow, hope that wil work.
Tried a few custom ROM's, all didn't work.
I'm starting to think about sending my HD2 to HTC, but I'm not sure if they can fix it. I've lost my warranty since there's Cotulla's HSPL installed, but I can't get it uninstalled because my HD2 won't install nbh-files.
I know I'm going to have to pay for this, but I rather pay than having a bricked phone.
no need to flash .nbh to remove hspl, , just run hspl.exe in bootloader and choose stock spl.
valkjuh said:
Hi all,
Yesterday I was playing Angry Birds (in Android), when screen turned black and my HD2 started to make a buzzing noise. I took the battery out, and since then my won't boot. When I turn on my phone I only get the white HTC bootscreen, wich is white/black striped, and it doesn't boot any further. I included a photo of the boot screen.
I already tried multiple hard resets, no effect .
Click to expand...
Click to collapse
Hi,
Did you find any solution for that problem?
Thnx
i must say. my phone (htc hd2) did the same so please did you find a solution?
Hello all. Forgive my newness, but I was an iOS person who just recently started working with an Android tablet.
My Viewsonic gTablet was not running very fast on Android 2.2, so I decided to upgrade it to Honeycomb (or at least to Gingerbread). I downloaded CWM8 for the gTab, and followed all instructions. I powered it on, used my volume keys to select the CWM file, and left it to sit for the appropriate length of time. Unfortunately, the installation failed to go through. Soon after, I started having problems with apps crashing as soon as they were opened, and having to be forced closed. I decided to go back to factory specs, and started that process. When it restarted the tablet, it came up to the three-birds screen, and a message in the top left says Booting recovery kernel image. It then just stays there, and does nothing. It doesn't seem to matter whether I power up with the volume key pressed or not - either way I get the same message. Manipulating the volume keys doesn't seem to do anything. Once I left it like that for ten hours while I was at work, thinking maybe it was just slow, but there was no change.
Following instructions from AndroidZoom, I loaded a recovery file onto an external SD card, to see if would boot from there. No luck. Still stuck on the booting message, with no option to select anything from the external card. Now for the million dollar (or at least $200) question:
Is there a way to access the tablet's internal SD card from my PC even though the tablet won't boot? I figure if I can, I will delete the new recovery file, and load a replacement file from viewsonic which I was lucky enough to find on the web.
ptrask said:
Hello all. Forgive my newness, but I was an iOS person who just recently started working with an Android tablet.
My Viewsonic gTablet was not running very fast on Android 2.2, so I decided to upgrade it to Honeycomb (or at least to Gingerbread). I downloaded CWM8 for the gTab, and followed all instructions. I powered it on, used my volume keys to select the CWM file, and left it to sit for the appropriate length of time. Unfortunately, the installation failed to go through. Soon after, I started having problems with apps crashing as soon as they were opened, and having to be forced closed. I decided to go back to factory specs, and started that process. When it restarted the tablet, it came up to the three-birds screen, and a message in the top left says Booting recovery kernel image. It then just stays there, and does nothing. It doesn't seem to matter whether I power up with the volume key pressed or not - either way I get the same message. Manipulating the volume keys doesn't seem to do anything. Once I left it like that for ten hours while I was at work, thinking maybe it was just slow, but there was no change.
Following instructions from AndroidZoom, I loaded a recovery file onto an external SD card, to see if would boot from there. No luck. Still stuck on the booting message, with no option to select anything from the external card. Now for the million dollar (or at least $200) question:
Is there a way to access the tablet's internal SD card from my PC even though the tablet won't boot? I figure if I can, I will delete the new recovery file, and load a replacement file from viewsonic which I was lucky enough to find on the web.
Click to expand...
Click to collapse
Do a code red, you'll be fine.
http://viewsonic-gtablet-for-dummies.webs.com/nvflash.htm
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
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
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.