i had a half bricked tablet. it was able to boot into recovery and i installed a rom and now it boots but the android sign is all screwed up and i cant get into CWM anymore.. am i done for?
View 4 Replies
I've been scouring the internet for the last view months since initially attempted to root my admittedly out of date htc view. A friend gave it to me in exchange for an old comp I built. I attempted through revolutionary to root, went through HTC and unlocked my device, continued to try and root it but found no proper software that worked to do so. Even tried something called mulitool which was pretty cool, but didn't get the job done. After a time I gave up on rooting, and my tablet powered down and I found myself stuck at the recovery screen. None of the options for clear storage, factory reset, or anything else proved fruitful. I removed my sd and was able to boot up fine. This was months ago. Now I'm having a similar problem only now even without SD card it's in a boot cycle where it boots to recovery for 30 seconds or so and shuts down, then back to recovery and like this ad infintum.
my screen reads:
relocked
**security warning
express pvt ship s on rl
microp 0656
hdboot 1.14 0005
radio 1.05.01
eMMC-boot
Recently I have rooted my android tablet and I was exploring what I could do. One guy was telling me about an app that can work with performance in game(ChainFire 3D). He said it lowers the pixels in the game to run better. I tapped the install button and it said rebooting now. It then started to reboot but then proceeded to get stuck at the boot screen. I tried doing a hard reset but it is still stuck. I have also tried flashing the stock rom, but I get installation aborted when I try and install it.
View 4 Replies View RelatedSo I was trying out the CM7 for xperia arc by the freexperia team. It was epic. so i also tried the CM9 release by them..
-> I downloaded the CM9 anzu for my arc S
-> Extracted the files
-> Used fastboot to flash boot.img
-> And then: fastboot reboot
Instead of the FreeXperia splash screen welcoming me.. i was given a black screen.. The phone does turn on.. but then there is nothing. No splash screens. nothing.
Is there anyway to boot straight into CWM?? recovery?? Did i brick my phone for good?
I have just bricked my tablet by puting another recovery.img.. and now the tablet only shows boot screen. How can i connect it to pc to usb adb to restore it...or another method?
tabletrestigio 5197D ultra
i have this phone (alps e1901 v77 fwvga) aka xtouch x507 (mt6577)
i flashed the original firmware from the supplier but since then the phone didn't boot
it wont charge also, but it's being recognized by pc and i still can flash on it.and i tested the battery its charged, and also there is current drain (~50 mA)when power button is pressed
my device is galaxy ace s5830i..i have already rooted my device and used CW Recovery and taken a copy of my original system.i wanted to set up a custom rom i restarted and reset and deleted the cash then installed the rom.i think it was Retribution beta then i wanted to update to that custom rom (MindCR ICS) all i did i restarted my phone of course went into R mode and reset and deleted the cash then installed that next custom rom .
after installing completed when i rebooted it only gave me (samsung galaxy ace s5830i) logo and doesn't open the system when i restart it doesn't go into recovery or download mode it only gives me again the same logo.i used odin v 1.81 and the latest version it doesn't recognize the phone and i can't go into download mode.
I was able to root my device correctly .. The issue started when I tried to install CWR by odin.. got into a starter loop or logo loop?
I then used my google fu to try and rectify the problem and ended up bricking it. But It can go into the down load mode. .
I try to understand android boot sequence on my JB (under CM10). I found some docs and there should be specific partitions (boot, recovery, system, cache, data).
My understanding of the boot sequence is now:
A) normal boot:
1) Power ON ->
2) bootloader ->
3) boot-partition where i flashed the kernel aka boot.img ->
4a) system-partition with the OS (libs, UI, etc) where i unpacked over CWM my customROM.zip ->
4b) data-partition, where i unpacked google-apps.zip and installed all the apps ->
4c) cache-partition with user data
B) recovery boot (adb reboot recovery):
1) Power ON ->
2) bootloader ->
3) recovery-partition with CWM where i may unpack all the .zip stuff to proper partitions, or restore from sdcard, etc.
Is this correct? I wonder, because i didn't installed CWM into recovery-partition. It cames from install of CM10 (fastboot -i 0xfce flash boot boot.img), so it must be in boot-partition and not in recovery?
So, next confusion: i looked up to /proc/mtd and i don't see neither boot nor recovery partition here:
Quote:
# cat /proc/mtd
dev: size erasesize name
mtd0: 19000000 00040000 "system"
mtd1: 00600000 00040000 "appslog"
mtd2: 06580000 00040000 "cache"
mtd3: 1a400000 00040000 "userdata"
I did a backup with CWM and loocked the data. There aren't boot, and recovery backups:
Quote:
# ls -lha /sdcard/clockworkmod/backup/2012-10-04.18.49.55/
d---rwxr-x 2 system sdcard_r 4.0K Oct 4 18:56 .
d---rwxr-x 3 system sdcard_r 4.0K Oct 4 18:49 ..
----rwxr-x 1 system sdcard_r 1.6K Oct 4 18:54 .android_secure.vfat.dup
----rwxr-x 1 system sdcard_r 54.6M Oct 4 18:55 cache.yaffs2.img
----rwxr-x 1 system sdcard_r 360.2M Oct 4 18:53 data.yaffs2.img
----rwxr-x 1 system sdcard_r 212 Oct 4 18:56 nandroid.md5
----rwxr-x 1 system sdcard_r 214.6M Oct 4 18:51 system.yaffs2.img
#
So, i think i didn't understand the boot sequence and partition schema corectly.
I have probably bricked my Huawei Vision by rewriting boot image.
However, I can connect* it to PC and it sees my phone as "Huawei Handset" (same with Windows and Linux). But Windows misses its drivers (non-bricked phone worked); Linux seems to work. No OS can connect to it using default (downloaded) ADB, nor Fastboot, nor SoftwareUpdateTool.
Its PCI ID is 12d1:c002.
How could I reflash it? I would prefer the ways without disassembling the phone.
How to boot the phone, so you can connect it to PC:
1. turn off my phone completely (vol up + power for 10 seconds - release power for a seconds and repeat it once again)
2. prepare USB cable, so you can connect it in few seconds
3. hold vol down + power and after ~1s, connect USB cable (still hold vol down)
4. when Huawei logo appears, release both buttons - your phone is connected now
I have an Allwinner A10 clone (Kurio 7), it is designed for kids but otherwise a standard android tablet. After hours of googling I rooted and installed CWM & Gapps (not included in the stock ROM). So far so good. The stock ROM was causing issues with some apps, it needed to go.
I flashed CM10 and it worked but no touch screen. It needed a compatibility flash to make it work. You can guess what's coming. I picked the wrong one and now the device does the following:
Reboot loop
Black screen (backlight though)
PWR+Vol up no longer gets to recovery
Vibrates constantly between reboots (due to wrong patch I'm guessing)
ADB picks up the device for a split second between reboots but "adb reboot recovery" does nothing. Even when using wait command. Tried "fastboot flash recovery cwm.img" after wait command, no luck. Is there anything else I can try?
I have a new ace 3 LTE S7275R. I tried installing CWM recovery found here: URL....I tried with odin 3.07 and 1.85Every time, odin shows success, but when trying to boot into recovery, the phone gets stuck at "recovery booting...."The phone is otherwise working...getting CWM to work? how can I return to stock recovery at least?
View 4 Replies View RelatedSo I just got my S4 rooted and everything seems correct. I then installed Rom Manager so I could start demoing some of the ROMs out there. Went through all the steps to flash Rom manager as the recovery but I cannot get my recovery to go to CWM, it just keeps going to the stock android recovery. I have googled the crap out of this and am coming up with nothing. in fact I have written several android apps but this just does not work.
My device is a Verizon Samsung S4 model SCH-I545 running android version 4.2.2 Kernal: 3.3.0-690088se.infra@S0210-13#1
I just recently try
View 2 Replies View Relatedi wanted to upgrade my galaxy s2 g i9100 and since that time i hve not been able to use the phone again.
i tried rooting it but after that i can not boot recovery anymore all that comes on the screen is SAMSUNG GALAXY SII with a yellow triangle.even if i press the up volume key+home key+power nothing happens.
I have a Karbonn A6 phone given to me by my friend because it was locked. It's asking for gmail user/pass but he doesn't have it. I tried to boot into recovery mode using Power+Volume Up button but all I get is a white triangle with an exclamation mark in it. I can't seem to go beyond that. USB debugging was perhaps not enabled unless it was enabled by default. There is no camera button, only power and Volume Up/Down. What do I do?
I just need to get this phone working somehow. Is there a way to use a computer and a USB cable to get it running?
I have tried using rom manager, holding the power button and selecting reboot recorvery, and by holding the power button and x. Each way I see the white m twice then the phone just boots up. I am running cm7 7.0.3. I have only had the phone for a week, I am trying to wait for the vigor. It worked fine Friday when I flashed cm7
View 4 Replies View RelatedI'm on a Galaxy S2 running Gingerbread 2.3.4, my baseband version is I9100XXKI1 and my kernel version is 2.6.35.7-I9100XWKH4-CL487028root@DELL136 #2
Using Odin3 v1.85 and S2 Root. (Superoneclick kept freezing on me)
My aim is to install Cyanogenmod 7.1.
So far I started off by trying to flash it with XWKDD Insecure, which I believe is wrong? However after rooting it, I installed ClockworkMod Recovery, downloaded the ROM and tried installing it - which is where the problem started - I kept getting the error in recovery mode 'Invalid whole-file signature'.
It just wouldn't boot in to ClockworkMod Recovery.
So after some digging around I managed to find a file to flash to my device for the CWM Recovery mode, tried it, and it worked. However, I still couldn't install Cyanogenmod from my SDcard.
I tried it a few times, wiped/formatted a few times and ended up getting my device stuck in a bootloop.
So, I've managed to get it out of the boot loop, and started fresh...
I flashed it with XWKH4 Insecure, unrooted, rerooted etc.
I've downloaded CWM again, downloaded the Cyanogenmod again, tried installing it, and once again it's gone back into Androids recovery and failed to install because of the 'whole-file signature' and failing to verify it.
I did post this in Q&A as well, however it doesn't seem to be as popular a forum as this one, I'm not really looking to wait for days for a response.
I rooted my phone using Z4 then used Titanium Backup for backing up and then recovery. Now while rebooting into recovery mode the phone took a long time in booting so I removed the battery and tried to reboot. But the phone makes the signature sound and after that only displays the following word 'spice'.
View 2 Replies View RelatedI flashed Omega rom today for my galaxy note 2. It uses Aroma installer which i think could be the problem. Basically I cant boot into recovery. The rom is also very laggy where people on its development thread are praising it stability! The device will stay on the 'Samsung galaxy note II gt17100' bootscreen when i try to.boot into recovery.
View 1 Replies View Relatedi have a cheap alwinner a13 tablet (simmtronics xpad x720) from indian manufacturer. It is stuck at cwm recovery it countineously boots to cwm after restart.I have no backup stock rom. But i can sideload zip from adb or external ed. And not able to mount internal sd or wipe cache.
View 5 Replies View RelatedI just tried to install an custom rom at my Android, i unlocked it on HTCdev`s site, but i think i was a little fast with the DooMLoRD_v2_ROOT-zergRush-busybox-su.zip
I then bootet the phone into fastboot, and did the command fastboot flash boot boot.img, this worked very fine but now the phone wont boot.
I think maybe the phone is unlocked, but it is S-ON. I have tried diffrent recovery modes with the fastboot flash recovery recovery.img etc, but none of them are working.
Now im sitting with a phone that wont boot at all, what to do?
Is it possible to keep going on with the custom rom install, or can i resett the phone into the stock rom?
ok, so I put the PB31IMG file on my sdcard, and the dinc_ota. I changed dinc_ota to update. (I did not name the file update.zip.zip) I powered down, I entered bootloader, and it loaded the PB31IMG and whatever. then I hit volume down and selected recovery. this brought me to clockwork recovery. I noticed the isntructions said to boot into STOCK recovery. well, I like a dummy ignored that and tried to apply the update.zip thru clockwork.
This is what I got:
CODE:.......................
So, is this because I tried doing it through clockwork recovery? is it because I didn't apply the first OTA update we got? what does that mean exactly anyways? is it saying I need to install the leaked froyo ROM, and then update the radio? How do I boot into stock recovery and not clockworks recovery? does this count as applying the update.zip once, meening if I do it again I'll brick my phone? should I sell this thing and get a samsung flip phone because I'm too stupid to own a Dinc?
I have an Android tablet (Diablotek D2-721, very cheap I know, but it serves its purpose) that is stuck in a boot loop. The real problem here is that this device apparently does not have any sort of recovery mode and being in a boot loop means it does not get recognized by ADB or any firmware flashing software.
I researched all day yesterday perusing forum after forum but almost every single solution requires booting into recovery.
My EVO 3D (Sprint) is rooted and is on android version 2.3.4 and I believe it's not an android official release, this is how it was given to me. I'm trying to install CM10.1
I installed ClockworkMod 5.0.2.0 using ROM Manager and since then I haven't been able to boot into recovery mode. I can get into bootloader but not recovery. I've tried powering it on with the volume button down, using the recovery reboot option, and tried using "Reboot into Recovery" in ROM Manager, but I keep seeing the same thing. It boots with the HTC logo then goes black then at this point i believe I should be seeing recovery mode but instead I see the HTC logo again and then it just boots like normal. Is there something I did wrong and is there a way to get recovery to work again?
I've been trying to track down a solution to my problem, but every solution seems to contain a "Boot into recovery mode" line which I cannot do. I attempted to update a rom that I had installed, and now I am stuck at the google logo with the unlock icon. I cannot boot into recovery with the volume keys and power, and now I cannot figure out how to use adb to recover the phone, as it cannot recognize it.
Is there anyway I can access this phone while it is in this state from my computer and recover it somehow. I tried following leads that people have posted in other threads, but it seems like most suggestions involve "Use adb", yet every adb tutorial involves the phone being in recovery mode. I've tried to uninstall and reinstall drivers via Wug's Toolkit, but when I plug my phone in, I am not able to install the drivers properly. I try to run adb items through the console, yet it does not recognize my device.
Is there anyway to install the necessary software I need and recover my phone while I cannot get past the google logo screen?
I am using a verizon galaxy nexus
I got the cat /proc/mounts here -
Code:
root@android:/ # cat /proc/mounts
cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
[code].....
I Have An Ainol Novo 7 Crystal Tablet..(Rooted With TWRP Recovery&Cyanogenmod 10.1 Installed).It Was Working Fine Till This Afternoon But I Don't Know What Happened Next..I Turned Off My Device And I Tried To Turn It On Again After Some Time But It Wasn't Booting...
I Don't Even See Any Boot Animation Or Android Logo That My Device Used To Display While Booting,The Screen Of My Device Lights Up Though..And I Can't Even Boot Into Recovery (I Have TWRP Installed),When I Try To Boot Into Recovery I Don't See The Android Logo That I Used To See But The Screen Of My Device Lights Up And Doesn't Boot Into Recovery.. I Tried Removing TWRP Recovery From My sd card And Booting Into Recovery But The Screen Lights Up For Like 5 Seconds And Then The Light Goes Off..
My Samsung Note 10.1(N8000) got stuck on boot screen at stock. No recovery only download mode. I don't know why, it was flat for about 2 weeks before I noticed.
Roms always and still flash successfully if I get the right version of odin, i think i have about 15 different odins from trying to fix this.
Things I've tried:
1.Flash stock rom
2.Flash custom recovery
3.Flash different versions of both 7+
4.Re-partition and repeat 1-3
5.Wipe the memory and repeat 4 with many many roms
why my tablet stopped the first time and why no roms are working to recover it. What is happening here? Is it corrupt memory or motherboard etc hardware? Is there a god .pit file or god rom that could work to make something happen? What should i try now?
This shows a successful flash which had no effect on the tablet afterwards
[URL]
I'm having trouble booting my LG Optimus G into recovery mode. I've rooted the phone and installed ClockworkMod recovery. When I try to boot into recovery, either from the ROMmanager app or by holding Volume Up and Power, it comes up with the LG logo and gives this error: Secure Booting Error! Cause: boot certification verify. It just stays like that until I press and hold the power button again until the phone shuts off entirely. Then I'm able to boot into the stock operating system and the phone works fine, but I can never get it to boot into recovery.
The error I mentioned above seems to be a well documented error on the internet, but it seems like other people that are having the trouble are completely bricking their phones. Mine is able to come out of it. All the solutions I'm finding pertain to a phone that's completely bricked and involve taking the phone back to stock. My phone works fine with the stock ROM, but I'd like to play with some custom ROM's.