Database Info

[q] help flashing freinds g1

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--------------------------

[Q] PLEASE HELP!!! Cannot Boot Nexus S!!

Hi everyone,
I'm sorry I'm quite new to this, and I'm afraid I've gotten myself somewhat stuck with my Nexus S. Yesterday I managed to root it, install superuser, as well as clockwork mod. Today I wanted to try a new rom and after some attempts, it seems I no longer have any working roms on my phone. After much searching with no luck, I turn to you guys for your expertise.
So I am able to see fast boot upon pressing the volume up and power buttons, and am certainly able to choose recovery and get into clockwork mod. Within clockwork mod I can mount USB storage, so I can transfer roms to the internal SD card. I've tried 3 or 4 roms, some say they install correctly, others not, and after trying to boot after any installation I simply get stuck at the google screen with the lock image at the bottom. The only things I have "deleted" is wiped the data and cache. I have no idea, but I think I may have erased the bootloader image or something else that I should not have that is required.
I have a i9020a model (non-4g model I believe), can you pleeeeeeeeeeeeeaaaassee help me!! I just want to get back to gingerbread 2.3.6, and my phone back up and running the way it was. I've become quite nervous after some searching with some saying a resistor mod is needed on the hardware!!

Your okay cause you can get into fastboot and recovery so don't worry. Maybe the rom you downloaded is not for your phone. Did you make a nandroid backup before flashing the rom? If yes then go into backup and restore from clockwork recovery to go back to stock.
Sent from my A500 using Tapatalk

If you can get to recovery, just flash the stock image FOR YOUR PHONE. Then you can go through and reroot..don't worry, you'll get the hang of it.
Sent from my Nexus S using Tapatalk

So my phone is not "bricked" as they say?? I'm not in big trouble?
I did not make a nandroid backup What kind of image am I looking for and how do I install it on the phone? I know my phone is of the variant i9020a, but how am unsure of how much more specific I should be looking for.
Looking at the following post: http://forum.xda-developers.com/showthread.php?t=1063664.
Should I try installing the Android 2.3.6/GRK39F/UCKF1 Radio/KA3 Bootloader option?

Choose the latest 9020a version of the FULL ROM, which is what you have already have eyes on.

I've tried installing the file I mentioned above, but I get a status 7 error when trying to install, and the install is aborted.
Could I get some more assistance please? Can anyone point me to a correct, full rom? Or perhaps I'm installing it incorrectly, could someone be so kind to outline the correct steps to a proper install?
Edit: I think the above mentioned file is for a GSM model, I'm sure I have the CDMA version.
Also, somewhat good news. I managed to install the oxygen rom, but for the 4g version and installed fine with no errors, but I have no service. What does this indicate, as I still want to restore back to a factory version (non-4g) of gingerbread 2.3.6.

What CWM version do you have? Is it 3.0.0.0?
Also, if you have no service, it's likely that you downloaded a ROM with an incorrect radio.
Edit:
If you have CWM 3.0.0.0, make sure to download the latest version, found in this thread: http://forum.xda-developers.com/showthread.php?t=988686 (use 5023-cyan.img). You flash this the same way you did CWM previously, though in the terminal make sure you type out the 5023-cyan.img file name.
Next, download the stock ROM from this thread: http://forum.xda-developers.com/showthread.php?t=1063664. Simply look for your phone version, and you'll find the correct software variant.
Maybe you've fixed your phone already; if not, I hope this helps!
I wish you the best of luck. Oh, and through problems like these, you come to learn a lot more about your phone. That's what I've found, at least.

At the thread you mentioned above there is a version with a different radio, you might want to give that one a try.
You also said that you only wiped data and cache, so maybe you should do a full wipe before. Not doing that can sometimes lead to problems.
Sent from my Nexus S using XDA App

To be brief, the phone is up and running as brand new! Thank you so very much everyone. It seems the error was with CWM, as I was able to install and boot a 4g oxygen rom on my phone, I went into rom manager, and at the bottom of the list was an option to upgrade to 5.x. Installed the CWM update, wiped everything and was able to install the factory rom, no issues, and everything works just as I remember
I have most certainly learned more about my phone, and I am going to look at it as a rather stressful learning experience rather than a mistake on my part.
But a sincere thanks to everyone once again, I posted this at like 4am here and had a response within a few minutes, I was pulling my hair out haha!

Flashing to stock rom will help you out. You can get stock roms from Internet simply by searching in Google...
Sent from my Nexus S using XDA App

[Q] NexusS (i9020T) hard bricked, at which step did I go wrong?

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.

New to Android and been reading.

Hello everyone. I received my Verizon SG3 shortly after it came out. I have been doing reading as I am very new to android. This is my first android phone. Previously I had an EnV Touch. Hated that thing, but it did the job. So any who I now have this awesome kick butt phone and it has all the Verizon crap on it I cannot get rid of. I have rooted and the bootloader is unlocked. I used a windows program to gain root and then used EZ unlocker to unlock the bootloader. I have been looking and looking to figure out what rom I want to start with, I want JB, but don't want a lot of bugs ATM as i don't have all that much time to play with flashing and being still so new I don't want to end up with a brick. I tried my harderst to figure this out by reading, but the info seams so spread out, I kinda want to try the CM10 9-6 as I have read it is stable and not many bugs. My main question is about kernels. Am I correct in thinking they will get flashed just like my rom will in ROM manager? Or do I need to flash through CWMR? How do I know what Kernel to use? I have been reading the CM10 takes a different kernel than say synergy or stock. Or will the stock kernel work till I load the proper kernel. If I knew about the kernel and how vital it was to go with the ROM maybe I wouldn't be so paranoid. I have a friend with a GS2 and he told me the kernel has to go with the ROM and if the two don't mach then you could brick. I can't afford a brick my first time around.
If you could give me some advice or point me in the direction of some more reading that would be great.
Thanks
JB

All ROMs come with a kernel in them. Typically you just stay with it unless you want some extra features or what not. There are aosp kernels and kernels based on the stock firmware. If you use a touchwiz based rom you need to use a touchwiz kernel.
I don't think it will brick it if you interchange them. It will just boot loop
Edit: you flash kernels in recovery just like a rom. if you change kernels without changing roms you need to wipe cache and dalvik cache through recovery also.
Sent from my Nexus S 4G using xda premium

Back up your IMEI before flashing anything, alot of horror stories floating around. Development has some fantastic guides. After that, most of the "big gun" rom's here have kernels, and are for the most part consistently the same flash method through recovery. Cwm recovery is solid and reliable, start with that until you feel comfortable enough to venture off. Make sure it's version 6.0.1.2 (regular or touch) for any jelly bean based rom.
Sent from my SCH-I535 using xda premium

I backed up the IMEI with the terminal emulator. So if the error occurred it would restore with the proper IMEI. Should I back it up any other way too?
Also I'm planning on using the Rom manager to flash the Rom. Do you not recommend that or should I do it manually with CWRM?
Thanks for the replies. I'm still getting my feet wet and know all about searching before asking. Used to program dish.
Sent from my Galaxy S3 using Tapatalk.

Your call, depends how paranoid you are! I would flash manually, it's a control thing for me, I know what/how/when all was done. Using 6.0.1.2 touch is awesome, speeds flashing up considerably.
Sent from my SCH-I535 using xda premium

I might have to try the touch. I have standard 6 on there. The one you listed. Rom manager gives me the option to load touch too. Friend uses Rom manager on his s2. Looks to just automate things a little.
What I don't know is if it wipes the appropriate areas first for a clean install or if it's doing it dirty.
Sent from my Galaxy S3 using Tapatalk.

Use the Synergy backup. If you lose your IMEI you just flash it again and it's back. Just make Nandroid backups and flash away. This is my first Android phone too and now I get why people become flash addicts, it's amazing what you can do. It's easy to relock and unroot if need be. Everything is easy if you take it smart and slow.
Sent from my SCH-I535 using Tapatalk 2

Here here!
Sent from my SCH-I535 using xda premium

Just stick to a couple rules and you will be fine. First is backup, backup and backup before flashing. Always stay within the Verizon SGS3 section, Sounds simple but others have made the grave mistake. When flashing kernels, stick to the software, ie flash a JB kernel to a JB rom, flash a ICS kernel to an ICS rom. You should not have any problems but if you do you always have a backup. There are many roms, just flash an try them, make sure to read through the threads to identify any issues that have been discussed. JB roms there are a couple, a TW based JB rom from a T-mobile leak that was ported to VZW SGS3 that works well, there are official and unofficial JB vanilla roms, ie CynogenMod. Stick to those rules, keep a back up, i usually will transfer a copy of my original backup to my pc just in case, and always backup to external sd card. Good luck and have fun.

You can also flash kernels via Odin I believe.

Odin, or just flash

I'm a little lost, I've been reading for days and can't seem to find my answer..here goes
Coming from droid1 were I could flash new to old and vice versa..had the s3 for a couple of weeks, I'm on beans 13 kernel lean1.0 and hd radio..the other day I was on clean 2.5, and before that on synergy..can I keep bouncing around like that, our do I need to do Odin thingie? I see were root'ers are Odin then taking this new update and looks like killer battery life..I don't really have a preference on roms , just nead a little help on doing it proper..txs

You can just keep flashing until you find a ROM you like. Odin is just basically when things are messed up and you need to go back to stock. I think it was RSD on the Droid 1.
Sent from my Galaxy S3 running Eclipse ROM V2.1

kintwofan said:
You can just keep flashing until you find a ROM you like. Odin is just basically when things are messed up and you need to go back to stock. I think it was RSD on the Droid 1.
Sent from my Galaxy S3 running Eclipse ROM V2.1
Click to expand...
Click to collapse
You can flash it just to go back to stock. Doesn't have to be cause you messed the phone up. I think it's also good to do it occasionally with a pit file to wipe/fix all partitions (not just /system and /data, but ones like the hidden radio/GPS partition etc.)
Sent from my SCH-I535 using xda premium

xsteven77x said:
You can flash it just to go back to stock. Doesn't have to be cause you messed the phone up. I think it's also good to do it occasionally with a pit file to wipe/fix all partitions (not just /system and /data, but ones like the hidden radio/GPS partition etc.)
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Well of course you can use it to just go back to stock, but the average user only does it when they mess up. I do agree though I personally even I find my daily driver like to start fresh then flash the keeper ROM.
Sent from my Galaxy S3 running Eclipse ROM V2.1

Have been rooted since day of pre-order delivery. Have flashed multiple ICS/JB TW roms. I stay away from AOKP/CM roms just because of loss of features so can't report on those. I have never lost wifi or GPS. Never had sim card error. Had no problems with TWRP and haven't used CWM since worked with Koush on Tbolt problems. We worked those out and I still run CWM touch on Tbolt. Used Amon on Rezound. Recoveries are what you feel comfortable with. I use whatever works best for the device although that is irrelevant to this subject. I still use the old school clean wipe of data/cache/dalvic cache/system for all flashes on all devices and all recoveries. Ultimately have never had a reason to use Odin or go back to stock since initial root. Only bugs I have seen are rom related and nandroid back to working rom fixed it. There are differing opinions on what I have just posted but I have had no problems with flashing anything on my last 3 devices and have never bricked a phone even though I may flash 10 times a day for multiple devs on multiple devices. Maybe the old school recovery devs were on to something. Beats me.

Kool..I'm catching on., slowly..
Now If I do an Odin with pda can I use a rooted oem Rom to accomplish this newest leak that is said to have killer batt life?

takota6 said:
Kool..I'm catching on., slowly..
Now If I do an Odin with pda can I use a rooted oem Rom to accomplish this newest leak that is said to have killer batt life?
Click to expand...
Click to collapse
Yes you can but they all have killer batter life. No need to Odin you can flash it in recovery. Only have to Odin stock RUU to get firmware update. If you do it could loose root and ability to unlock boot loader. You will have it as long as you keep it. As soon as you flash another rom it will wipe that one and you will be on the base that the rom is based on. This is why the devs update to latest bases whether they be leaks or official. Best you can do is flash newer radios and kernels unless the ROM Gods tell us to update firmware and then it will be checked and deemed safe. Never Odin/flash an OTA/leak unless it has been cleared by the Android Gods. I have only used Odin once and that was because that was only way to root on original pre-order. :laugh:

be sure to back up internal sd card
takota6 said:
I'm a little lost, I've been reading for days and can't seem to find my answer..here goes
Coming from droid1 were I could flash new to old and vice versa..had the s3 for a couple of weeks, I'm on beans 13 kernel lean1.0 and hd radio..the other day I was on clean 2.5, and before that on synergy..can I keep bouncing around like that, our do I need to do Odin thingie? I see were root'ers are Odin then taking this new update and looks like killer battery life..I don't really have a preference on roms , just nead a little help on doing it proper..txs
Click to expand...
Click to collapse
Don't forget to back up internal sd card. Odin will wipe it when you flash.