First of all i'd like to thank anyone who takes time to answer this because this has been driving me nuts for the past 2 days.
Now that thats out of the way; I have a Droid 2 and i'd consider myself a noob with this phone. I rooted the phone yesterday and had problems with ROM manager flashing cwm 2.5.0.8, so what i did was downloaded cwm3 off the internet and moved it onto my SD, renamed cwm3 to 2.5.0.8 and all of a sudden my recovery system works. Once i got that all taken care of i began messing with ROMs. My brother put the beta version of tanzanite on and bricked my phone, i fixed that. Once i got rid of tanzanite i tried using gingerblur 1.3 and got stuck in a bootloop. Right now im in the process of trying to use gummyjar 2.5. More so to the point, what my main question is, is since i'm using clockworkmod 3 would that restrict my phone from being able to use any semi-older ROM versions such as the ones previously stated?
Again, thanks a bunch to anyone who can answer my retardedly long question
Related
Hello everyone,
I was hoping someone could help me out with a bit of a problem I'm having here. I'm becoming rather scared and a bit desperate.
I just tried to install cm6 onto my nexus one, which I have done on a previous nexus one without any problem. I unlocked the bootloader, flashed amon ra's recovery image, and then updated the radio. I did all of this manually, not using clockwork or anything of the sort. I proceeded to install cyanogen's and google's addons, and everything seemed to go smoothly. I rebooted the phone and it got stuck in a bootloop. It flashes the nexus boot image and then the blue cyanogen one but just gets stuck there and tries to go at it again, failing every time. I have repeated this entire process twice, both times making sure I wiped the data and the cache, and the same unfortunate event has happened both times. Please could anyone help me out here?! I really need someone's help right now. I'm kind of panicking.
Thank you everyone for your replys. Any help is welcome help! I'm fairly knowledgable with ADB and rooting. I've been doing it quite a while now.
CM6 is very beta at the moment. If you're running one of the RC builds, try flashing a nightly build. It might make things better (or worse).
i dont know what im doing wrong but last week i could install gingerbread with no issues other than the market. because of the market issue i use NVflash to go back to square 1 and start over. so i installed VEGAn 5.1.1 with no problems. after about a day i was reading up on other gingerbread roms so i went to try one and it would install but never finish booting. so i nandroid back to were i was and try the rom i had before with the market issues, that one didnt work either.
what am i missing?
ps i cant get logcat to read any farther than from recovery.
in recovery logcat says "/sbin/sh: logcat: not found"
[solved] got it ^.^
ok dont know what the [email protected]# i did but i got it working.
for any of you that care on how it started working its going to be a long post.
basically on my quest to fix this damn thing i decided to use nvflash which didnt work the first 5 times, so i used the original recovery image rather than the rooted one. that semi-bricked it so it would only boot into APX mode. so after an hour of searching XDA i just flashed the enhanced image (like in the guide on the dev forum) and holy crap it worked and installed VEGAn 7 without updating.
dont know how it fixed it but it did.
Mods can you please delete this thread
I said I would flash cyanogenmod on a friends G1 because he was fed up with 1.6. I've flashed many custom ROM's on several different devices before but I've made a mess of things with this G1 and I can hardly hand back an unusable phone so I would really appreciate your help.
I rooted the phone using Androot, backed up the apps and settings using titanium backup and then the texts using a text backup app. I then downloaded Rom manager and flashed the latest clockworkmod recovery. Next I downloaded the latest official cyanogenmod rom for the dream/g1 and placed it on the phones SD card using my computer. I then re-opened rom manager and used it to select the zip file from the sd (to flash it) on prompt I checked two boxes one to wipe data and one to wipe the dalvik cache and pressed ok.
The phone rebooted into the recovery wiped the stuff, supposedly flashed the rom and rebooted. However it got stuck on the t-mobile g1 boot screen(it never showed anything else first or anything after) I left it for ages with no joy. I then tried wiping from the recovery and flashing again - same thing so i put cm5 on and tried flashing that. Same problem. Then i realised that it probably would not work because I would need to use DangerSPL as the /system partition is too small on the dream/g1. To be honest at this point I can't be bothered with to do that and this guy will be happy with anything above 1.6 to be honest so I thought I would try and flash CM4 because that's based on Eclair I believe (and so it not require I use DangerSPL or any other method to repartition the NAND). However, I tried it twice and still no luck.
At this point I'm somewhat panicking as I cannot seem to make the phone boot and it isn't even mine! Is anyone able to help?
Anyone? Please?
Look, at this stage I will forget custom roms etc. If anyone can tell me the easiest way to get this phone booting android again i would be very grateful.
Even if you could just tell me exactly how to restore it to stock 1.6 from here?
I have flashed roms on phones before - never had a problem but this is driving me crazy - please help!
wollac11 said:
Hi I said I would flash cyanogenmod on a friends G1 coz he was pissed off with 1.6 but im having trouble and I can hardly hand back an unusable phone so i really need your help.
I rooted the phone using Androot, backed up the apps and settings using titanium backup and then the texts using a text backup app. I then downloaded Rom manager and flashed the latest clockworkmod recovery. Next I downloaded the latest official cyanogenmod rom for the dream/g1 and placed it on the phones SD card using my computer. I then re-opened rom manager and used it to select the zip file from the sd (to flash it) on prompt I checked two boxes one to wipe data and one to wipe the dalvik cache and pressed ok.
The phone rebooted into the recovery wiped the stuff, supposedly flashed the rom and rebooted. However it got stuck on the t-mobile g1 boot screen(it never showed anything else first or anything after) I left it for ages with no joy. I then tried wiping from the recovery and flashing again - same thing so i put cm5 on and tried flashing that. Same problem. Then i realised that it probably would not work coz i would need to use DangerSPL coz the /system partition is too small on the dream/g1. Tbh i'm tired so I cba to do that and this guy is not that technical so he will be happy with anything above 1.6 so I thought I do CM4 coz thats 2.0 or 2.1 i seem to remember (and it not require I use DangerSPL) - tried it twice and still not luck.
HOW THE HELL CAN A GET THIS STUPID THING TO WORK AGAIN!??
MAJOR PANIC AS THIS IS NOT MY PHONE - PLEASE HELP!!!
Click to expand...
Click to collapse
Try this thread: http://forum.xda-developers.com/showthread.php?t=803482. I hope it helps.
It's been way too long since I rooted mine to be of any real help but I shall try nonetheless.
Firstly, there is a guide in the G1 forum to unroot and get back to stock firmware: Here (but note that I've never done this).
I must stress though (admittedly from memory) that if you have flashed an SPL or radio image at all, be VERY careful about the order in which you revert back to stock (or go to get a custom ROM depending on which way you decide to go). The G1 is very picky, and flashing things (mostly SPL and radio IIRC) in the wrong order will brick the device. That said, if you follow the instructions you find to the letter you should be OK. But yeah, read twice, flash once.
There is a lot of information in the stickies in the G1 forum. It could take a while to wade through but it should all be there. Failing that, post in the Q&A or General G1 subforums and I'm sure a current user will help you out.
I apologise if I've just posted a bunch of stuff you already know/have read - like I said, I've not used the phone in a while - just trying to offer what I can.
Thanks
No worries now guys i've done it! It was quite complicated but its all sorted now. If anyone is trying this and has the same (or similar) issue then pm me and I will tell you how I sorted it.
Otherwise thanks guys and you can conciser this thread:
---------------------closed--------------------------
Hi everyone, I had a problem with my previous nexus s (I have since gotten a working replacement) and I was wondering where exactly I messed up so in the future I can avoid this
Here is what I did on my previous phone:
1. I flashed ics onto my device from the ota update package from androidcentral, it was 4.0.3. (This worked great and I had it on my phone for 2-3 months before I tried the next steps.)
2. I rooted my device successfully using the guide at nexusshacks.
3. I also flashed TWRP recovery (fastboot) and superuser using the above guide/links
4. When I would turn off my phone it would boot to a screen with a red triangle and an opened android bot. So what I would have to do is flash twrp recovery everytime I turned the phone on just to get it to work.
5. What I wanted to do was keep the stock rom but still have twrp recovery without it making me reflash it on every boot. So I clicked install and tried to flash the stock rom (update package from the link in step 1) with twrp recovery. It then turned off my phone and hard bricked it. I couldn't turn it on anymore and a new battery didn't fix it.
I was able to get a replacement now and I was just wondering at which step did I go wrong? I THINK that I should have wiped my cache before I tried to reflash the stock rom but maybe I'm way off base here. This is why I posted a question here so hopefully some of you guys can help.
I did think about posting in another thread, but I didn't wanna threadjack or anything... and his problem also seemed a bit different then mine. Also, sorry about not being able to provide the specific links it won't let me post them until I've posted 8 times.
I don't know for sure but team win recovery has been reported to corrupt the device's efs directory. I've even had problems myself using clockwork recovery. I've moved on to razor recovery and haven't looked back.
This is the most flash-friendly phone I've ever owned, and razor recovery rivals amon ra (which was awesome on my g1 and evo). I really think it may have just been the recovery you were using... Somebody correct me if i'm wrong.
Sent from my Nexus S 4G using Tapatalk
I had once corrupted one of the partition. I fixed to by flashing stock recovery and stock rom.
Use adam outler's unbrickable mod tool. It can be found in android development section.
Sent from my Nexus S using XDA
Thanks for the replies.
That's interesting about twrp... I didn't know that. Truth be told, the only reason I went for it over other ones like clockwork mod was because the UI looked pretty nice and easy to use. Also the guide I followed at nexusshacks used that, so I wanted to stay consistent with it.
jishnu7, it's a little late for that now however as I actually have already received a working replacement from my carrier, but in the future if something ever does go wrong (hopefully not) I will definitely check that out.
The main thing I'm wondering is if it messed up because I tried to reflash the stock rom essentially over top itself (was hoping that by doing that, it would stop making me reflash twrp on every reboot) or if it was because I didn't wipe the cache before the flash.
Also, what I really wanted to do with my phone was to keep the stock rom but be able to overclock my cpu/gpu. I was hoping I could set different overclocks for different things (I've heard of kernels where you can downclock your phone when the screens off and have it overclocked slightly while you're using it, that would be something I'd like to have). I figured to install those kernels I would have to root my phone, replace stock recovery and install superuser so that's why I tried to do that. Once again, I'm pretty new to all this stuff for my phone.
Sorry to bump this thread again, but I would really like to know how I could avoid what happened to me for the future. I think it's because I flashed the stock 4.0.3 rom over itself (was hoping that by doing that twrp recovery would stay on the phone after reboot).
What I would like to do is install something like CM9 or AOKP and use the Matr1x kernel so I could undervolt or overclock my phone.
I seriously dont get how u hard bricked your phone...
the reason you are thinking is you reflashed stock rom without wiping cache, as per my experiece its not at all the reason
now, whats my experience??
...I have some fault with my nexus device and I'm working on it,,and I did everything I could do...one of the thing out of those things was reflashing stock rom without wiping,and i did it quite a several times...my device never hard bricked,,however it was soft bricked for many times,,and i recovered from it
so reflasing a stock rom over stock rom, over ICS, over some themed custom rom,will not hard brick your device, you must be missing something none of your steps sounds suspecious
P.S:- pulling out battey while flashing something like this sounds suspecious, never tried though
I'm not sure what happened either to be quite honest with you. Since giving it another shot now with my new fresh phone I have had great success!
I did everything I wanted to do all in one go. Rooted it, install CWM touch, install AOKP (went with milestone 4 cuz I heard newest build 29 has some bugs) + gapps and installed matr1x kernel 18.5 bfs.
The only thing I did different from last time was installing CWM touch (instead of twrp) and flashed aokp this time (instead of reflashing 4.0.3 over itself).
I would just avoid step 2 at all cost.
The nexus s hacks dude is a tool.
*What ROM should I get for my phone and will it solve my issue for data? and what am I doing wrong to install roms?*
About two weeks ago I finally got around to rooting my Android Razr Maxx so that I might speed it up since it had been laggy. I was able to root my device with no issues and overclock it to solve this problem. I began to expand to other things rooting would allow me to do and attempted to use a mobile data tweak-er to get a speed increase. At first it seemed to work great until at one point about a week later I restarted my phone and couldn't access my mobile data, I could only get WiFi and the 4G bar is always there with signal but remains grayed out. I started looking around for info and eventually asked two friends of mine who both noticed I had no VPNs listed in my phone and said that was why,I don't know how this could of occurred but both told me I could fix it by getting a new custom Rom if I didn't want to do a factory rest. If this is true I would appreciate it if someone could help me find a ROM that works for my phone. I'm currently using the Motorola Droid Razr Maxx. stock version 4.1.2 system version 98.72.165.XT912 I have Safestrap 3.11 installed already and followed numerous videos trying to get a new ROM to work, so far I have tried Wizzed Bean Jelly Wiz and Eclipse but all 3 give me a boot loop when I try to get them working and I always have to revert back to to my stock Rom after my attempts. I'm guessing there was an incompatibility I wasn't aware of in all 3 cases.
Any help with any of this would be most appreciated and I apologize ahead of time as I may be ignorant to some things involving this question