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)
Related
I've tried to look for this problem and haven't found anything similar. If it's already been addressed please direct me to the previous thread, if this is in the wrong place please move it.
I rooted my Galaxy S II a while ago and it's been working great. I wanted to try Cyanogen mod 7 and so I followed the instructions on their website. Trying to use ROM manager gave me a weird error message telling me that there was an invalid signature or something, despite toggling everything and wiping the cache to turn it off. So I followed the "method via recovery" instructions. I did everything exactly as it is there, including the Google apps stuff, and it all seemed to work perfectly. Then I rebooted it hoping for it to boot into CM7, and instead, when it turns on it goes to the screen saying Samsung Galaxy S II with the yellow triangle underneath, and stays there. Every time it turn it on it goes to that screen and doesn't change. It's now been like that for half an hour. I can start it up into download mode, and I've tried flashing zImage to it again, but no change.
I have a NANDroid backup (it's backed up with CWM anyway), and I've copied the backup to my computer, but I have no idea how to apply it when the bloody thing won't turn on.
I'm using Linux with Heimdall (the cross-platform Odin clone).
Please help me. Unfortunately I have no internet in my flat so I won't be able to see any advice until tomorrow unless it;s given in the next ten minutes. God I really hope the thing's ok.
Hi
Do you have jigg? ( if you don't have it buy it from ebay or ask some friend of you )
With jigg you can enter download mode and then flash the stock rom.
Pull battery, wait 10s, then boot while holding power+vol-up+home. This should get you in recovery. Then restore nandroid.
Sent from my Transformer TF101 using xda premium
TheGhost1233 said:
Pull battery, wait 10s, then boot while holding power+vol-up+home. This should get you in recovery. Then restore nandroid.
Click to expand...
Click to collapse
I can't believe it was this simple, I knew power+vol-down+home got tme to downloading but I didn't know that got me into recovery. Everything's recovered now.
Thank you Dutch people!
This problem probably has shown up a lot and usually I would take my time to look around before asking but I'm feeling lazy so here goes:
I recently put in a new-ish ROM (it's am US stock type ROM that I found on here) and all works well except for one thing - the CWM refuses to load. At first I was getting the dead android with the red triangle sticking out and so I decided to use ROM Manager to flash CWM again. Might have been a bad move since I'm still fairly noob-ish but anyhow it didn't work. Now whenever I try to go in it just freezes. If I try manually it shows the RCK box, android box, etc and just stays there. When I try to do it through ROM Manager it stays at the first ASUS logo. Can someone refer me to a guide I could follow or even give me a solution to fix this? I will be very grateful. Thank you in advance.
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.
Ok guys so, I had installed badadroid but after reading around the internet about how certain ROM was faster I decided I would try it, I flashed the uninstall zip in the badadroid thread and followed the instructions on the blog of that certain developer HOWEVER at one point I'm asked to flash a new FOTA and bootfiles with multiloader, I did that but at some point I messed up, now my phone boots up to this screen and sometimes to the recovery provided by the other ROM, following the steps to install that ROM and rebooting doesn't help at all and I keep getting stuck in this screen, my phone shuts down automatically a few seconds later and multiloader doesn't recognize it.
I still have hope because, when plugged in, it boots past this screen and into said recovery, however it seems like Bada was wiped during this process and I can't find a way to go back now (I only found out this happened right after I had already done this)
Is there any way to force it into download mode? I need my phone
Thanks
EDIT: Managed to get into download, will see what I can do, I guess I can work things out now, you can close the thread
Also, sorry for the bad image quality, I took that with my laptop's camera
Fidelator said:
Ok guys so, I had installed badadroid but after reading around the internet about how certain ROM was faster I decided I would try it, I flashed the uninstall zip in the badadroid thread and followed the instructions on the blog of that certain developer HOWEVER at one point I'm asked to flash a new FOTA and bootfiles with multiloader, I did that but at some point I messed up, now my phone boots up to this screen and sometimes to the recovery provided by the other ROM, following the steps to install that ROM and rebooting doesn't help at all and I keep getting stuck in this screen, my phone shuts down automatically a few seconds later and multiloader doesn't recognize it.
I still have hope because, when plugged in, it boots past this screen and into said recovery, however it seems like Bada was wiped during this process and I can't find a way to go back now (I only found out this happened right after I had already done this)
Is there any way to force it into download mode? I need my phone
Thanks
EDIT: Managed to get into download, will see what I can do, I guess I can work things out now, you can close the thread
Also, sorry for the bad image quality, I took that with my laptop's camera
Click to expand...
Click to collapse
In any case, don't worry, you can't break wave so easilly.
This Fota have default boot to android and not bada, and if you installed Nand bada is indeed dead.
But you still can flash full bada with Multiloader and you still can install Android with this fota/bootfiles, just make sure to follow installation procedure of your rom (by the way, this fota is compatible with ALL roms)
Hello,
I wish I could explain my problem quickly and clearly, but I lost count on the amount of times I wiped, flashed and reset my Tablet so... I just hope someone comes up with a genius idea, because I'm desperate. I've tried everything.
Today I decided I wanted to try and find a better ROM I could install on my Ainol Tablet, and after doing some research I found out there was a 10.1 version of Cyanogenmod that was apparently quite popular.
I followed a tutorial I found on slatedroid.com (Flashed CM 10.1, Gapps and compatibility file) and only after I found out I just flashed a ROM built for the previous model of my tablet. When I reset it it came up as if it had done a Factory reset (same firmware but everything came up in chinese).
Then I went on and managed to find a tutorial for mine; repeated the process.
Right after doing that I re-read the tutorial (I would love to attach the link but I am a new user and am not allowed to...) and realised I was supposed to update my stock firmware to the latest version before flashing CM on it (apparently so they had the same kernel). Luckily, I had made a backup with TWRP so I went back to it and went looking on my PC for said firmware.
When I managed to find it, I realised the wifi on my tablet was gone. Whenever I switch it on, it goes back off after a few seconds. So no internet.
Then I thought I could just get that update file from my PC and copy it through USB. But that wasn't working either, my laptop will not recognise it whenever I plug it. The tablet won't even recognise a USB flashdrive.
Lastly, I realised there was a miniSD card port so I tried getting the file in through that as well. In this case, the tablet displayed a "preparing SD card" message but nothing happened afterwards...
I'm completely stuck. I have tried several times going back to Factory settings through TWRP, or reloading that backup I made, erasing Dalvik/Cache every single time, but the problems are still there. Everything else seems to be working though...
I did some research and it does look like I flashed a ROM with the wrong kernel so all the drivers are gone... (When the tablet is off and charging it displays a battery that used to stand vertically. Now it comes up horizontally...).
If that was the case, would anyone have any clue on anything I could do to fix it? Any files I could get rid of? Or maybe some secret menu on TWRP I haven't taken into account...?
Any ideas would be extremely appreciated. Please help! :'(
Thanks in advance.