Hey all, this is my first post on this forum. I registered just to let my voice be heard.
Let me just say that I have done extensive research into these problems but I don't want to brick my phone so I want to know the direct steps for me.
OK my problems are:
Upon turning on the phone the original Motorola logo is gone and is instead replaced by:
"Unlocked. PwrReason: PWR_KEY_PRESS. OS will boot in 5 seconds. Press a key to stop countdown. Avaliable Modes are: " and lists 14 different modes I can choose
This happened after I accidentally deleted my pds folder or something of the sort. I must've partitioned something accidentally and as a result my phone did not boot the next time around. It booted after I did a battery pull but gave me the next problem.
Upon booting into CM10.1 I noticed that the soft keys would not work. The entire screen was recognized as one big touch surface.
I deduced that some file was deleted which makes the screen recognize the soft keys, so I proceeded to do some research into it. The methods I saw to do were doing some sort of pdsfix which is not recommended unless necessary, which in my case is very necessary. I can boot into Romracer's recovery (5.0.2.7 I believe it is) as well as my OS. Everything is working except for those problems I listed. I am not sure if my phone can boot into fastboot but I can try. Please post your answers because I really need to get my phone working perfectly again. At this point, it is only useful for texting and a little music (and settings). I can't go into much else without restarting the phone each time (you must know why).
EDIT 15/04/13
-----------------------------------------------------------
I just flashed pdsfix(gingerbread).zip and I am now able to use my phone at normal speeds and even overclock if necessary. I was running epinter's CM10.1 Rom
Fixed half the problem!
Okay so after many hours of trying, I managed to install the drivers for fastboot on my computer and did the fix for the pds file.
First I downloaded moto-fastboot.zip and extracted to my C:/ drive.
Then I tested if my device was recognized. It didn't recognize it at all, so I went into device manager.
In device manager there was my problem. I saw fastboot with a yellow exclamation sign. I right-clicked it and directed it to where I had previously downloaded fastboot drivers. (Found them here: FASTBOOT DRIVERS
It installed nicely and when I tried the commands listed in Method 2 on this page PDS Partition Fix it worked perfectly!
So I proceeded to restart the phone, no issues. But the Motorola logo at the very beginning is still not there. It says unlocked at the top left and displays the same options as before. The phone is still fully functional without it, but I want to get it back. I will be doing more to fix this though.
But the best part is that, my soft-keys are working perfectly! :laugh: I do notice a little lag in the system but that will be fixed soon. Hope this helped anyone who didn't know what to do.
P.S. If you find a way to restore the Motorola logo on boot, please tell me!
http://forum.xda-developers.com/showthread.php?t=1423763
Logo and animation
Mojar7070 said:
http://forum.xda-developers.com/showthread.php?t=1423763
Logo and animation
Click to expand...
Click to collapse
Perfect! Thanks much for finding that for me. I now have the problems fixed except that my cpu won't clock above 608 mhz even when I put the min clock slider higher than that value.
I suspect that perhaps I flashed the froyo pdsfix instead of gingerbread. Maybe that is causing the problem. I'll try and post my results soon.
My Atrix 4g is fixed!!
Wow I can't believe I finally fixed it! It was as I suspected. After downloading the pdsfix(gingerbread).zip I rebooted my phone into fastboot and proceeded to flash the zip. And who would've guessed it? I am now able to clock at usual speeds including the 1000MHz of old ^_^. I am sooo glad I found this forum. If anyone had similar problems you can try the steps I did.
P.S. For the record I was running epinter's CM10.1 Rom for the Atrix 4g. I may go to Neutrino's in the near future, but I am just glad to have my phone back in working order :laugh::laugh:
Hi there freaks,
I'm an owner of this chineses piece of... art. And um it's kinda laggy so I decided to use the Greenify and SDMaid apps to get it to better shape. After spending few days in a row trying to find a way to get it rooted, I've found this forum and the thread where they presented a way to root most of the tablets on the market. Well I was scared cause I did not find a single tip about how to turn back the changes (in case I'll brick it-my wife would kill me;p), any way I decided to give it a shot and it worked. I keep getting info that root was not found sometimes but I need to reboot it and start over and in fact it seems to be rooted.... anyway I need to speed it up a bit more.
Can I install the CyanogenMod on it? And I can - which partical version will work fine with my tablet? I've found CM roms for Sanei N10, Sanei N83, N90 etc etc but nothing for N77. I can't even compare the roms cause I have no idea what is the exact hardware installed in it and don't know any way to find out. I could look for a specific CM rom that has drivers to my device but don't know what's installed in it. I know that there is probably no way to get back to the original Android 4.0.3 ICS which I have installed right now.
All I can provide you with is the model name and basic info like:
Device name: Sanei N77 Elite
CPU: Allwinner A13 1.5GHz
GPU: Mali -400MP
RAM: 512 DDR2
Int.Memory: 8GB
Display: IPS WVGA 800x480px, TFT
Wifi: 802.11bgn
No 3G support - but they say I can have it working with these modems: E1916, ZTE AC2736, HUAWEI E1750, HUAWEI EC122, HUAWEI EM770W
Thank You for Your attention and possible help
---> anyone?
I have this piece of art as well.
After a lot of hassle and searching around I managed to boot CM10 on it. (just need a few patches to make it fully working, was too lazy at first)
Basically all you need is this:
http://forum.xda-developers.com/showthread.php?t=1886460 - ROOT, select old special or new standart root, whatever works (depends on firmware installed)
http://forum.xda-developers.com/showthread.php?t=2189640 CWM based recovery
http://forum.xda-developers.com/showthread.php?t=2343531 CM10 ROM for Allwinner A13 Tablets + patches
BTW, if you boot into recovery, format system and then reboot tablet without any ROM flashing, it will become bricked as there is no way entering recovery mode without adb (as far as I know) on this piece of art. In this case you would have to flash one of the stock firmwares (download flashing package from there) and then do everything all over again (root+install cwm)
EDIT: Since my touchscreen is not working now (haven't flashed patch for it in the first place) and as it turned out USB debugging in this CM10 build is off by default (so I don't have access to ADB nor CWM), I need now to do this whole process all over again, lol.
EDIT2: It turns out there is not patch for ft5x_ts (touchscreen included), gonna pull it from stock fw and make flashable zip, will upload it here as well.
Ok I found it there http://forum.xda-developers.com/showthread.php?t=2189569
just found out some one replied to my post here i already gave up on modding this but i will check it all again when i get back to my pc. do you have it working finally? how is the performance with cyanogenmod? thanks mate
k i'm reading it all now, lot of things are not clear enough for me yet, can you lead me step by step? or do you have a ready working image of the system that i could simply flash into this tablet? how? thank you
im stuck on installing cwm it installed perfectly fine but when im trying to enter cwm on booting nothing happens except the ics is loaded in emergency mode....
btw this tablet has only 3 buttons which is power. vol+,vol-. no enter button at all... could you help me on this?
survivor1986 said:
just found out some one replied to my post here i already gave up on modding this but i will check it all again when i get back to my pc. do you have it working finally? how is the performance with cyanogenmod? thanks mate
k i'm reading it all now, lot of things are not clear enough for me yet, can you lead me step by step? or do you have a ready working image of the system that i could simply flash into this tablet? how? thank you
im stuck on installing cwm it installed perfectly fine but when im trying to enter cwm on booting nothing happens except the ics is loaded in emergency mode....
btw this tablet has only 3 buttons which is power. vol+,vol-. no enter button at all... could you help me on this?
Click to expand...
Click to collapse
Please... anyone?? Cant install CWM, tablets boots normally but in emergency mode instead of CWM While using built-in recovery mode I cant do anything except navigating Up and Down in the android recovery menu Power button does nothing in this case....
HELP!!!!!!))
will the external usb keyboard work in the recovery mode??? i will buy one in that case...thanks
Hi, everyone! I'm new to this forum(so sorry if I post this in the wrong place), and I recently received an Cosmote Move(Alcatel OT-908 rebranded) from one of my friends. He said it belonged to his wife(she is a bit experienced in IT) but she bought herself a new phone so he gave me to find it a good use.
I turned the phone on, booted Android(after 5 minutes of showing me a blue, distorted and unrecognizable logo). The phone was slow, cluttered with tons of apps and almost unusable. I barely reached the settings, looked at the settings, and it had Android 2.2.3(the kernel & baseband info were empty). It was rooted and had custom recovery installed on it.
I wanted to install a new custom ROM on it, and as I am an CyanogenMod fan, looked for an unofficial CyanogenMod 7 ROM. After minutes of searching, I downloaded one from 4shared( big mistake, I know ), moved it to the SD card, and booted the recovery(CWM 5.0.2.8 - petite edition or something like that). I chose "Apply update from SD card" and selected the zip. It took 10 minutes to install, then something like this appeared: "CyanogenMod 7 LEWA", or something among those lines. I thought that was alright and I chose "Reboot system now". Then the phone was stuck in a boot loop, showing the distorted logo and rebooting again and again. The custom recovery combination(Power + Volume UP) didn't work anymore, so I couldn't do anything. I looked for some zips/images for fastbooting, but they didn't work or showed this: "Error: package has no android-info.txt or android-product.txt" so I gave up and searched the web for some tips, but none worked.
Has anyone here been into a similar situation and solved it? If yes, how?
Also, no BBCode, HTML or Markdown here on XDA?
I also forgot to tell you that the phone originally ran the stock Android 2.2 Froyo ROM and I tried to install CyanogenMod 7 (2.3 Gingerbread) on it, without installing the stock 2.3 first. That may be one of the reasons I can't do anything. I mean, it still turns on, but recovery is inaccessible and the ROM isn't working(distorted logo, then bootloop). Someone on AndroidForums told me to erase the kernel/boot partition and the recovery one and reflash them back. For the kernel I chose ChocolateKernel by cheqolada(Linux 2.6.32.9-pref for 2.2) and for the recovery I used an .img file that I found here on XDA. Unfortunately, it didn't work at all. But at least, instead of that distortion, now I get a white screen
Scatter files!?
New Update: I found an article deep here on XDA about a tool named SP FLASHTOOL by MediaTek(ARM arhitecture creator?) that can reflash the Alcatel OT-908, but it needs a scatter file. No idea what that is, but I'll do some research. In the meanwhile, if somebody has that file, please PM me or post it here.
Edit: I just looked up the term, and scatter files only work for MTK SoC phones, while the OT-908 has a Qualcomm one. Bad luck... :crying:
I am an idiot. On this phone, the recovery combination is Power+Home+Volume up, not Power+Vol up. I managed to flash a ROM from here and now everything is okay. I might make a tutorial on unbricking, ROMs and recovery once I can post links and stuff.
I've tried everything, I can't access the recovery and I can't seem to find any .img files and I can't get the run_me.sh to work either.
Please help me, I'm using an Xperia U, just before this happened I made a backup using TWRP (version 2.7.1.0.1 I believe), then flashed CarbonRom.
Because my keyboard recently stopped working, it disappeared during writing and didn't remember any words and it was awfully slow. I found it it was a RAM problem.
So I picked carbonrom because I saw that it was smaller, saved some RAM, but now I can't boot back into recovery and I don't have any GAPPS at all, my phone is basically useless.
I can get in, but nothing appears to work and I can't start into recovery.
I've even tried to boot it into fastboot and bootloader, but it only flashes blue or green for a second then it starts with the default boot into system.
I don't know what to do, and I really need my phone.
Edit; Oh, I am so sorry, I was tired when I made this thread, I was meant to post in the newbie thread.
Could someone please just merge it in or move it (or just remove it and tell me, again I'm sorry)
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?