Database Info

[Q] How bad did I brick my Kyros 7005??

Okay, where to start.. I think I have bricked my phone pretty good.
Here is the approximate list of things that happened.
I wanted to try to update to froyo, so I downloaded z4root, worked beautifully
Followed all the directions to install clockwork mod (including reading far enough ahead to find out the one in the directions was for the 7015, but gave the link for the 7005 version later) - Worked like a charm
BACKED UP SYSTEM as instructed
Then here is where things went south. I attempted to install the Cyanogen Mod froyo based. I followed the directions, including backing up softmac and wpa_supplicant files. And it would not start up. I could get it into recovery mode but not to start fully. I tried doing the restore, it couldn't mount the SD Card where the backup was. Being knowledgeable enough to dangerous in Linux, I used ADB Shell and tried various things to try to find out where the SD Card or recovery image failed. I had also been trying to locate FWDN as I saw people had done fixes with that, but I couldn't get it to load in FWDN "Mode". I figured if I could replace the recovery program on there that doesn't work with the one that does, it should in theory allow me to reboot into the correct recovery mode and let me pull the files from my SD Card. After about 15 minutes of shuffling around, I ended up mounting the \system folder where I found a file called recovery. Looked to be the right size. So I made a modified batch file that would instruct it to load from that folder.
After that mistake, all of the sudden, the vtc driver that I had installed did see the unit. I was like Joy! Joy! I fired up fwdn but since I didn't have the original files that it "liked" I used an lk.rom, but I think it wasn't from an X5A but from a lonpad. Now I don't even get COBY on the screen.
But wait, I'm even more dangerous. I got the hardware ID that it's currently using on the USB bus, edited first the vtc ini file to see if I can reload a different rom. It detects it, but FWDN gives me "bad boot" error or something like that. But I'm a trooper, if I'm gonna kill it, I'm gonna kill it good. I change the SDK/ADB driver to recognize the device. And it seems to recognize it. Then I went to try "fastboot flash recovery recovery.x5ag.img " which I had NEVER been able get the unit into fastboot mode, and it goes through and does it. Then I do a fastboot reboot to see if I can get it to come up in recovery mode, but I can't.
Then the final bright idea comes up on me.. Hey, I have the backup from SD card, what if I zip it up, call it update.zip, and do a fastboot update?
Now ADB can make some kind of connection to it, but when I try to shell I get:
- exec '/system/bin/sh' failed: No such file or directory (2) -
ADB State always reports device or unknown never bootloader
ADB remount comes back with remount failed: Invalid argument
ADB push into the / or /system folders (in an attempt to push a copy of sh there) fails saying read only file system
ADB push to /sys comes back with failed to copy: No such file or directory
So, that's where I am.. I think I really really REALLY bricked this thing... although the fact that I can still ADB to it leaves some shimmer of hope.
Thanks,
Joe

can u get into the boot loader at all? If so you are not Bricked you will just need to reinstall the entire system using fast boot. You may be able to restore the default OS using an update.zip file. It may be named something different for your device. All you do with that is place it on the root of the SD card and when the bootloader boots it finds the file and flashes the phone.

I can't get fastboot to recognize the device, it goes right to the ADB bridge. Where I can run some limited ADB commands that are recognized.. If I could get it to start up in fastboot mode, that would likely solve the issue, provided I can get the correct working update.zip file, rather than me trying to fudge one from the clockworkmod backup.

do you have any hardware buttons on device? turning on with volume up or down (or back) gives you differing USB ID's to device manager - obviously you want fastboot mode. (use device manager on ADB Bridge (Details) to get your ID - i think its DEED for fastboot and D00D for fwdn)
otherwise... you can force boot a new bootrom. It's what I did on my telechips device. Find tcboot.rom - put it in the same directory as fwdn
1. Open your device
2. Unsolder your battery + terminal
3. While turning on the device, place a short - screwdriver/pin etc - across pins 7/8 of the NAND chip (for 5 seconds)
4. FWDN should bring up a message about flashing bootrom
5. Reboot (and resolder battery cable)
Note: this obviously is pretty hardcore - but i went from brick, to black screen brick, to full restore via this method.

[Q] Recovering from soft brick

Hi all,
I was fiddling around with a rooted android 7 inch tablet (its a china-made tablet i believe - TWD_MID) with android 4.0.4 installed. In order to hide the status bar i tried to follow certain tricks (replaced the /system/app/settings.apk and /system/framework/android.policy.jar). This caused the tablet to go into a bootloop (the boot animation kept on playing)
The obvious solution offcourse was to install a new custom ROM (since i unfortunately did not hav a backup ROM) ; however doing it manually i came across these problems:
1. The tablet doesn't seem to have any sort of bootloader / custom recovery mode. I've tried power +volume up and power+ volume down; even did adb reboot-bootloader , adb reboot [recovery] but nothing - the tablet just kept booting normally and going into bootloop.
2. There seems to be some problem with fastboot as well - almost all the commands entered along with fastboot yield "<waiting for device>"
I even tried using uniflash to install a custom rom; the tablet reboots twice and uniflash gives a success message; but in reality there seems to be no change in the tablet
Till this point though, adb was working properly
Out of sheer desperation (I know i shouldn't have, but still ) I used adb push to push all the entire /system folder from the extracted folder of custom rom into the /system of the tablet.
Now i can't even use adb shell - any adb shell "[command]" gives the error :
- exec '/system/bin/sh' failed: Permission denied (13) -
Please if possible can someone give me some advice??
I'm hoping to find a way to:
1. Get adb shell working again
2. Install and enter into some sort of bootloader/custom recovery mode on the tablet; so i can install a rom from TF(ext sd) card
I want to get my tablet working again....
Please Help...
Thanx a lot in advance...

[Q] Black Screen Brick / Android Logo - Different than the others

A pretty girl here in Zambia found out I know a bit about technology and brought me her Tab 2 GT3100.
Upon Power or USB insertion it boots to the 2nd Android Screen, and that's where it sits over and over again.
Upon trying to enter Recovery Mode - I get the fallen android with the stomach open.
Upon trying to enter Download mode, well, I can't.
I've managed to get an adb connection off and on upon bootup and can even get a logcat.
I cannot enter download mode via adb reboot download.
I can get access to the root filesystem via adb shell - and just for fun, I deleted contents of /dalvik-cache /cache and many 3rd party apps in /data
Still, the unit doesn't want to boot.
Any idea on this one? Is there a way that it can be reflashed via an SD Card? Can I push an image via ADB? ADB shell?
If I can get this to work, my days might just become brighter.

tiredofit said:
A pretty girl here in Zambia found out I know a bit about technology and brought me her Tab 2 GT3100.
Upon Power or USB insertion it boots to the 2nd Android Screen, and that's where it sits over and over again.
Upon trying to enter Recovery Mode - I get the fallen android with the stomach open.
Upon trying to enter Download mode, well, I can't.
I've managed to get an adb connection off and on upon bootup and can even get a logcat.
I cannot enter download mode via adb reboot download.
I can get access to the root filesystem via adb shell - and just for fun, I deleted contents of /dalvik-cache /cache and many 3rd party apps in /data
Still, the unit doesn't want to boot.
Any idea on this one? Is there a way that it can be reflashed via an SD Card? Can I push an image via ADB? ADB shell?
If I can get this to work, my days might just become brighter.
Click to expand...
Click to collapse
buddy as you are not able to boot in download mode or recovery i think it is bricked as you say black screen is observed
try triangle away to unbrick it
or customer care center always welcome you

tiredofit said:
A pretty girl here in Zambia found out I know a bit about technology and brought me her Tab 2 GT3100.
Upon Power or USB insertion it boots to the 2nd Android Screen, and that's where it sits over and over again.
Upon trying to enter Recovery Mode - I get the fallen android with the stomach open.
Upon trying to enter Download mode, well, I can't.
I've managed to get an adb connection off and on upon bootup and can even get a logcat.
I cannot enter download mode via adb reboot download.
I can get access to the root filesystem via adb shell - and just for fun, I deleted contents of /dalvik-cache /cache and many 3rd party apps in /data
Still, the unit doesn't want to boot.
Any idea on this one? Is there a way that it can be reflashed via an SD Card? Can I push an image via ADB? ADB shell?
If I can get this to work, my days might just become brighter.
Click to expand...
Click to collapse
Try it it recognised with pc odin. ...
If yes flash stock rom your issues will be solved
Dont Forget To HiT Thanks Button

Droid ultra kitkat update not installing

Recently I found out there was a kit kat update for my droid ultra it downloaded the update using 4G LTE and now and decided to install it then the phone shuts down and powers back up on its on I thought it was part of the update but this is the 100th time it's done it ive been waiting 8 hours for it to stop but it just keeps going it's not even showing any sign that it is updating!!!
I tried booting into recovery to factory reset it but whenever I select recovery it just boots up the phone normally HELP PLEASE!!!

response
droidusr2014 said:
Recently I found out there was a kit kat update for my droid ultra it downloaded the update using 4G LTE and now and decided to install it then the phone shuts down and powers back up on its on I thought it was part of the update but this is the 100th time it's done it ive been waiting 8 hours for it to stop but it just keeps going it's not even showing any sign that it is updating!!!
I tried booting into recovery to factory reset it but whenever I select recovery it just boots up the phone normally HELP PLEASE!!!
Click to expand...
Click to collapse
It appears as if you have installed some kind of rooting tool. The reason why the phone boots up normally after you choosing Recovery is because you don't have a custom recovery tool installed.
To solve this same problem, I factory reset my phone. (this is assuming that you have windows) To do this, install the Motorola Device Manager (google it and find the motorola support page, you can download it there) and reboot your computer.
Then connect the usb cable to your computer and download the android SDK platform tools from here -
ht tp://developer.android.com/sdk/index.html#download
^remove the space in ht tp because i can't post links
Extract the /sdk/platform-tools folder to a location which you can easily access.
Then, open command prompt and type
Code:
cd [mydirectory]
for example, if i stored the platform-tools folder on my desktop, i would type
Code:
cd C:\Users\[myusername]\Desktop\platform-tools
then open the bootloader (fastboot) by holding POWER and VOLUME-DOWN instead of just the power button when trying to boot.
OR type this into command prompt (your phone has to be turned on for this)
Code:
adb reboot bootloader
then, once your phone is in the bootloader (do not press anything on your phone at this point), type this in command prompt
Code:
fastboot -w
Remember, this will wipe all your user data / cache but it should make your phone work again. I'm not sure how to do this without factory resetting so if there are any users who are more experienced, feel free to post your better solution. thank you.

Thanks
Thank you so much currently I can't try out your method but it looks like it could work THANK YOU SO MUCH I'm going to try tonight and I'll tell you how it went. I really don't mind factory resetting as long as it saves my phone im all right thanks again :laugh:!!!
Pacnet_ said:
It appears as if you have installed some kind of rooting tool. The reason why the phone boots up normally after you choosing Recovery is because you don't have a custom recovery tool installed.
To solve this same problem, I factory reset my phone. (this is assuming that you have windows) To do this, install the Motorola Device Manager (google it and find the motorola support page, you can download it there) and reboot your computer.
Then connect the usb cable to your computer and download the android SDK platform tools from here -
ht tp://developer.android.com/sdk/index.html#download
^remove the space in ht tp because i can't post links
Extract the /sdk/platform-tools folder to a location which you can easily access.
Then, open command prompt and type
Code:
cd [mydirectory]
for example, if i stored the platform-tools folder on my desktop, i would type
Code:
cd C:\Users\[myusername]\Desktop\platform-tools
then open the bootloader (fastboot) by holding POWER and VOLUME-DOWN instead of just the power button when trying to boot.
OR type this into command prompt (your phone has to be turned on for this)
Code:
adb reboot bootloader
then, once your phone is in the bootloader (do not press anything on your phone at this point), type this in command prompt
Code:
fastboot -w
Remember, this will wipe all your user data / cache but it should make your phone work again. I'm not sure how to do this without factory resetting so if there are any users who are more experienced, feel free to post your better solution. thank you.
Click to expand...
Click to collapse

Will factory reset erase root??
One more thing I actually am currently rooted by using RockMyMoto so I think that is why the update didn't work but 1 last question when I factory reset will it erase root? I don't mind if it erases root but my main concern is that if root somehow stays I won't be able to do the software update.
Pacnet_ said:
It appears as if you have installed some kind of rooting tool. The reason why the phone boots up normally after you choosing Recovery is because you don't have a custom recovery tool installed.
To solve this same problem, I factory reset my phone. (this is assuming that you have windows) To do this, install the Motorola Device Manager (google it and find the motorola support page, you can download it there) and reboot your computer.
Then connect the usb cable to your computer and download the android SDK platform tools from here -
ht tp://developer.android.com/sdk/index.html#download
^remove the space in ht tp because i can't post links
Extract the /sdk/platform-tools folder to a location which you can easily access.
Then, open command prompt and type
Code:
cd [mydirectory]
for example, if i stored the platform-tools folder on my desktop, i would type
Code:
cd C:\Users\[myusername]\Desktop\platform-tools
then open the bootloader (fastboot) by holding POWER and VOLUME-DOWN instead of just the power button when trying to boot.
OR type this into command prompt (your phone has to be turned on for this)
Code:
adb reboot bootloader
then, once your phone is in the bootloader (do not press anything on your phone at this point), type this in command prompt
Code:
fastboot -w
Remember, this will wipe all your user data / cache but it should make your phone work again. I'm not sure how to do this without factory resetting so if there are any users who are more experienced, feel free to post your better solution. thank you.
Click to expand...
Click to collapse

Tried the method and it worked!!
I tried what you said and it worked perfectly but it still remembers my Wifi, wallpaper and all it showed the setup screen and I set it up so hopefully im in the clear the phone is downloading the update right now.

It will not allow the update and you will still end in boot loop. Need to remove root first: http://forum.xda-developers.com/showthread.php?t=2577029

[Help] Blu Vivo 4.8

Hello friends, I need your help...
Since i did a Dalvik-Cache clean on my phone, it got stuck on the bootlogo...
I can't find anywhere the stock rom and the scatter file to try amend this with SPTool since I dont have CWM or TWRP.
If there is a way to just get my files, pictures and music back will be enough help...
:crying:

Since no one bothered to help me, I managed to find a solution.
Will share here what i done.
1- Downloaded adb and put at C:/adb
2- Downloaded my phone usb/adb drivers.
3- Put my phone into factory mode by holding Volume-down key and power
4- By doing previous step and connecting the usb cable on the phone to pc, is possible to use adb commands
5- Used the command = adb pull /storage/sdcard0 C:/adb/Phone-Files (Can't start "adb shell" otherwise file/folder copy is blocked) from the cmd at the adb folder
6- Waited a hour and half to get everything from my phone to the folder = C:/adb/Phone-Files
I'm on my way to learn how to fix the Dalvik-Cache deletion.
Maybe getting the stock rom somewhere and using pull may solve... :fingers-crossed: