Related
So i just updated to an SPL for a Hero ROM, and now i'm stuck on the t-mobile G1 screen, i can get to the console, but if someone can walk me through how to mount the SD card using ADB (from the very begining) it would be a great help. This way i can try to update the firmware, or resort back to the original radio/spl/firmware. I need a very easy to understand set of instructions, because every time i have tried to do something with ADB it never goes well.
all you need to do is re-flash your current rom your using no wipe needed.
Whats the command to do that, i've been trying to load the new ROM onto the SD card through the command prompt. and it doesn't seem to want to work.
Bassicly i use the adb push command to try and shove a ROM on to the SD card like this
adb push JAChero2.0r6.zip /sdcard/JACHero2.0r6.zip
and then i change the name to update.zip and it still applies the OLD SPL update.zip file i have in there.
Try removing the old update file first through the adb shell. I have run into a couple instances where it is doing what you are describing. I always found that removing the current file first will resolve it.
adb shell
# rm /sdcard/update.zip
# exit
adb push JAChero2.0r6.zip /sdcard/update.zip
Then try to flash the update through recovery.
Got it fixed, THANKS!
im stuck at g1 screen as well....what did you do to fix this?
Im stuck on G1 boot screen, cannot get into FBOOT or anything!
What can I do??
if none of the button combos work like home+power or camera+power or any others then you can either call tmobile and play dumb or have the sweetest paperweight at the office.
crpercodani said:
if none of the button combos work like home+power or camera+power or any others then you can either call tmobile and play dumb or have the sweetest paperweight at the office.
Click to expand...
Click to collapse
Will it cost me if I contact tmo?
I'll play it dumb, but when the phone ends up at some engineer, and they see what I've flashed on, will they just fix it, or report it to tmo? (as i've broken the t&c's!)
As much as having a paperweight sounds cool, I could really do with a phone!
BTW, thanks for your help!
IanVaughan said:
Will it cost me if I contact tmo?
I'll play it dumb, but when the phone ends up at some engineer, and they see what I've flashed on, will they just fix it, or report it to tmo? (as i've broken the t&c's!)
As much as having a paperweight sounds cool, I could really do with a phone!
BTW, thanks for your help!
Click to expand...
Click to collapse
If the phone won't boot using home + camera then they can't prove it's been rooted (unless they somehow read the nand...) so they should replace it for you without charge.. Same thing could happen if the battery was pulled during an over-the-air update.
they wont bother checking anything, just be sure it is bricked and your good. Most likely they just take it apart and jtag it or something like that. And if you got the phone from tmo and are with them then no its free.
AdrianK said:
If the phone won't boot using home + camera then they can't prove it's been rooted (unless they somehow read the nand...) so they should replace it for you without charge.. Same thing could happen if the battery was pulled during an over-the-air update.
Click to expand...
Click to collapse
crpercodani said:
they wont bother checking anything, just be sure it is bricked and your good. Most likely they just take it apart and jtag it or something like that. And if you got the phone from tmo and are with them then no its free.
Click to expand...
Click to collapse
Yep, it wont boot using any key-combo.
Its reading the NAND/using JTAG which is what I'd do (i work with embedded devices!).
I might say the battery died while the update was happening, gotta act dumb! (which I must be for managing to brick it in anycase, after all, Im a softy-eng!)
And I'll get a new phone! Or reconditioned?
Many thanks ppl!
Well.
If you manage to help this guy (http://twitter.com/r3nrutSite/) and the ppl on this thread (http://forum.xda-developers.com/showthread.php?t=309291) to JTAG the G1, please tell me.
I'm stuck with a bricked G1 here in Brazil.
Currently there is no way of bringin a g1 back to life short of giving it a heart transplant<new board>
see Brick Thread
Tp2 brick eny help??????
plis help
i was unlocking my phone (the HTC Touch Pro 2 <sprint>) and I was using a Diamond unlocker , but during the process there was a connection error and now my phone seems to be bricked. I can't get it to even turn on, get to a bootloader screen, or anything even remotely close.
The one odd thing that it does though, is when I connect it to my computer, it pops up and my computer recognizes there is a device there. In my Device Manager there is an unknown device called: Qualcomm CDMA Technologies MSM. I have tried every combination of two buttons, including holding down the reset button with all of them, but nothing gets me anywhere.
If anyone could help, I would really appreciate it. there's eny way to save it???
SHADE86 said:
plis help
i was unlocking my phone (the HTC Touch Pro 2 <sprint>) and I was using a Diamond unlocker , but during the process there was a connection error and now my phone seems to be bricked. I can't get it to even turn on, get to a bootloader screen, or anything even remotely close.
The one odd thing that it does though, is when I connect it to my computer, it pops up and my computer recognizes there is a device there. In my Device Manager there is an unknown device called: Qualcomm CDMA Technologies MSM. I have tried every combination of two buttons, including holding down the reset button with all of them, but nothing gets me anywhere.
If anyone could help, I would really appreciate it. there's eny way to save it???
Click to expand...
Click to collapse
Theres a app for that!
an app for recovery a htc tp2 brick
Ace42 said:
Theres a app for that!
Click to expand...
Click to collapse
really an app??
please tell me where i can find it
and what steps i must follow,
am desperatedm thank`s
SHADE86 said:
really an app??
please tell me where i can find it
and what steps i must follow,
am desperatedm thank`s
Click to expand...
Click to collapse
http://tinyurl.com/yayoq48
App used: Firefox
I'm not a total noob to rooting as I've already rooted my G1 and am running cyanogen's mods for months now. My problem is on a different phone.
This dream was dropped in water months ago (that's when I purchased my 2nd on craigslist). The touchscreen wouldn't work so I was stuck at the setup screen. I read on many forums, xda included that it might eventually dry out and today I found that it was indeed working fine.
It works fine on stock 1.5 ota update crc1 but now that I rooted one I want this one rooted as well. This is where my problem starts. I'm trying to rollback using the dreaim.nbh found inthe latest "how to root" thread in the dev forum. Problem is I can't load the image. I powe up holding camera and power button, get to the multicolored bootloader, insstructions on the grey/whitish screen say press power button to load, and then I am stuck.
Power button does nothing and the phone is stuck on that screen until I pull the battery. Been through this process 5+ times, with redownloaded image (file is not corrupt) My concern is Ill end up bricking but I really want root. I'm think their might be water damage on the phone but everything else works fine.
Any suggestions for a workaround or a way to troubleshoot the problem? Thanks in advance!
-Air
nbh
heres a link to where you can get the nbh dwnload this one nd try agian.
http://coolpstuts.blogspot.com/2009/07/all-download-links.html
no dice
pistol thanks for the try but it didn't work. same 87.3mb file, rc29, same result.
the greyish white screen loads, but the update (rollback) never starts. Does anyone know of another way to load the dreaim.nbh image? or heard a similar issue?
are you sure you grabbed the t-mo image?? go to the original how to root your phone thread and grab the t-mo image, nothing has changed so there is no reason for us to have an updated thread other than to confuse people even more
my problem is not the rc29 image
tubaking, my problem is not the rc29 dreaim.nbh image. I have consistently found the same image in many threads on xda. my problem is that i cant get it to load. this thread was not created for general rollback issues and def not to confuse people with another how to.... i am trying to figure out why my US G1 (with a noted history of physical abuse) won't load the image.
Was not implying that this thread would be a how-to and confuse people, merely that we have so many and people are constantly asking how to do something even though the steps didn't change. The physical abuse your phone has sustained "should" have no effect on the image flashing. I would suggest you format your card again(not in windows as windows seems to screw up a lot), so long as you are using the correct image and a fat32 formatted card you shouldn't have any problems, does the screen pop up and say "no image found"
airmaxx said:
tubaking, my problem is not the rc29 dreaim.nbh image. I have consistently found the same image in many threads on xda. my problem is that i cant get it to load. this thread was not created for general rollback issues and def not to confuse people with another how to.... i am trying to figure out why my US G1 (with a noted history of physical abuse) won't load the image.
Click to expand...
Click to collapse
hmmm, have you tried re-formatting your card?
trying it now
reformatted at home using gparted but I'll try paragon now that I'm at the office.
tubaking, thanks for the advice and willingness to help. it does not say no image found. It actually shows the steps that it needs to install including, radio_vz, and a few other things i cant recall right now...
hopefully the reformat will do the trick. I will try to format the entire card fat32 for now and then add my ext3 after. reporting back shortly....
still not working
so reformatted again to fat32, used paragon, gparted, and built in format on the G1 still the same result
grey white screen, reads the image.... then stuck at:
Code:
DREAIMG.nbh -
BOOTLOADER -
RECOVERY -
BOOT -
SPLASH1 -
SYSTEM -
USERDATA -
RADIO_VZ -
Press power button
to start update image
Press action button
to cancel update image
and then I'm stuck
So even after you press the power button to start the update, it just stays at that one screen and never gives any "ok"s next to any of the listings?
exactly
no oks, just hangs there
I've been letting it sit since before my last post, about 45 mins so far and still nothing. I may have imagined it but when i did this process last week it felt like it was getting hotter, but still nothing happened
also I remember doing this on my other G1 that is already rooted, so I know how easy this step should be
Stupid question, but are you making sure not to rename the original DREAIMG.nbh to anything else other than what it is? Some people make the mistake of thinking they have to rename it to update.zip or make the mistake of not leaving it in capital letters (although I don't know if that matters). You have said you have downloaded the file multiple times so I doubt this is the case but I'm just spitballing here
no rename
In my desperation I had considered that really stupid idea for a moment but thought better of it. I don't want to end up with a brick i haven't renamed it, consistently used dreaimg.nbh
airmaxx said:
In my desperation I had considered that really stupid idea for a moment but thought better of it. I don't want to end up with a brick i haven't renamed it, consistently used dreaimg.nbh
Click to expand...
Click to collapse
I wasn't suggesting to rename it, I just wanted to make sure that you never had renamed it to anything but the original filename DREAIMG.nbh
its all good
directmatrix, I understood your post. I was just saying i had considered renaming it to update.zip in an effort to get something going. I appreciate the spitballing, maybe we'll hit something that I missed!
airmaxx said:
directmatrix, I understood your post. I was just saying i had considered renaming it to update.zip in an effort to get something going. I appreciate the spitballing, maybe we'll hit something that I missed!
Click to expand...
Click to collapse
I re-read your original post and was curious as to whether the power button could be the culprit considering that its needed to flash the image. Perhaps the water may have damaged the power button interface. I can't imagine that it would be the problem considering your able to get into the rainbow screen via power+camera. Have you tried pushing it harder, many times, on the side etc?
i did, tried holding it for a 10 count, multiple presses, long press. I'm pretty sure the problem is not with the button itself because it works fine when I have the phone booted up and press power to turn it off.
When I first posted I was hoping someone might know of an alternative button combo that might have the same effect of loading the image from that greyish white screen
there is no way to write the image through adb right?
I have a G1 that was given to me stuck on the exclamation point screen.
I've tried various update.zip methods, When i try to update it says it can't read from the recovery. It'll install the update like normal it seems, but then when it reboots, go right back to the exclamation point screen.
It was never rooted. Not sure what version was on it when it bricked
I've searched the forum all day trying to find a thread like this.
Does anyone have any insight into how to fix this?
Thanks
PusherRobot said:
I have a G1 that was given to me stuck on the exclamation point screen.
I've tried various update.zip methods, When i try to update it says it can't read from the recovery. It'll install the update like normal it seems, but then when it reboots, go right back to the exclamation point screen.
It was never rooted. Not sure what version was on it when it bricked
I've searched the forum all day trying to find a thread like this.
Does anyone have any insight into how to fix this?
Thanks
Click to expand...
Click to collapse
Not sure what rom you tried to put on it but I would bet the camera button is stuck.
billquinn1 said:
Not sure what rom you tried to put on it but I would bet the camera button is stuck.
Click to expand...
Click to collapse
Should be the home button in this case. If it was the camera he'd see rainbows, with home it takes you to recovery (the ! screen)
exactly. thanks for the help.
I replaced the buttons and now everything works.
Hi guys, my first post here (although have done some reading in the past year) and in dire need of some help. Last night I tried to root my phone. I followed instructions from a sticky post on here, and from another sticky post on another forum.
Before going through how I got there, I'll state what condition my phone is right now, as this may be more reader friendly. I turn on the phone and get the fastboot screen (tricolour). I can reset with call+menu+power. Goes back to bootscreen. Only way to turn off the phone is to remove the battery. If I press trackball+power, a blue LED comes on, the screen stays black. Turning on the phone with camera+power doesn't make a difference. Turning on the phone with home+power doesn't make a difference.
The screen, on turning on, says the following:
'DREA110 PVT 32B RUUNBH
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
Sep 2 2000
Serial0'
Before it gets to the screen, the screen briefly flashes white and says
'Loading...
No image file!'
I'll try to decribe what exactly I did leading up to this in as much detail as possible, however it took place from 11pm to 4 30 am, and not fully understanding the whys behind what I did, I may not be able to recall it perfectly. Please ask if I haven't provided enough details. I installed the earliest android software and did the telnet commands through telnet, downloaded on the market. I downloaded an app called root.apk and followed the instructions. I got to 'Step 3 - Protect Root' and it said 'Root Protected'. I then got JesusFreke's 1.5 EU rom and renamed it 'update'(.zip) and placed it in my root SD card directory. I loaded the software on. I THINK the mistake I made was not having the radio image (I don't even know what it is or why I need it) before trying to load it. I've since put it on and it hasn't made a difference.
Anyway, I turned on the phone after the install, and it became stuck on the android screen. At this point, home and power and camera and power both worked to provide me with different boot screens when turning on the phone. I did a hard reset. This brings me to where I am now.
Is my phone bricked? I read on a guide here the difference between soft and hard bricking - from what I understood, this seems to be somewhere in between - hopefully if it's a brick it's a soft brick! Any help would be much appreciated, as we all hate to live without our G1's, lol! Looks like I'll be going back to my Nokia 6210 and trying to send this thing for replacement back to T-mobile. Please help guys!
Many thanks
Michael
search around the forums, as far as i know, if you can get to the fastboot, your g1 isn't bricked
Yep, agreed.
In my old G1 days I had the same problem and it was because I didn't have an image file on my SDcard.
You're not bricked but I've since gone from G1 to Hero to Nexus so I'm not what you need to do but it is SIMPLE, I remember kicking myself when I sorted it.
HTH.
thanks for the prompt response guys. Very relieved to hear that it might not be bricked.
I just tried adding two separate image files (one at a time) to the root directory, but it hasn't made a difference. These are the details of what I added:
First I put in all three of these:
Android 1.5
Radio Image ota-radio-2_22_19_26I.zip 9181622 aeecdb49b74a0d4bb67f9d8af70c1889
System Image signed-dream_devphone_userdebug-img-150275.zip 38027127
5ca85a135ff1ddd41643237577cb8ec4
Recovery Image signed-dream_devphone_userdebug-ota-150275.zip 46907411 01c19785eef97b06409f52fed568feff
and then the system image for 1.6 just in case. Is this a noob mistake? I'm very unfamilar with system images, would be really great if someone could link me to the file I should try and put there for the image file!
Thanks again guys
well since it goes into fastboot, is there a way you can flash the recovery in fastboot, and try from there?
sakumaxp said:
well since it goes into fastboot, is there a way you can flash the recovery in fastboot, and try from there?
Click to expand...
Click to collapse
I'd certainly love to try any ideas how I'd do that? If you let me know i'll do it now. atm i'm not aware of any buttoms/commands which work in fastboot, but I've never used it tbh.
yeah to be honest, im not sure how to do that either, i just remember i was lurking around this forum and i saw a previous thread, that had a similar problem and someone mentioned the tip i gave you, so if any senior members or anyone know how to do this, please explain
Tranquility__89 said:
thanks for the prompt response guys. Very relieved to hear that it might not be bricked.
I just tried adding two separate image files (one at a time) to the root directory, but it hasn't made a difference. These are the details of what I added:
First I put in all three of these:
Android 1.5
Radio Image ota-radio-2_22_19_26I.zip 9181622 aeecdb49b74a0d4bb67f9d8af70c1889
System Image signed-dream_devphone_userdebug-img-150275.zip 38027127
5ca85a135ff1ddd41643237577cb8ec4
Recovery Image signed-dream_devphone_userdebug-ota-150275.zip 46907411 01c19785eef97b06409f52fed568feff
and then the system image for 1.6 just in case. Is this a noob mistake? I'm very unfamilar with system images, would be really great if someone could link me to the file I should try and put there for the image file!
Thanks again guys
Click to expand...
Click to collapse
I may be wrong here (if I am come round and strangle the cat).
But I don't see any .img files?
They are all zips? you need to have the image files UNZIPPED an as .img IRC.
OK, I unzipped the folder and put a folder in the root which had the .img files in them.. still didnt work. because i was trying to put them on to the sdcard through my girlfriends old nokia, it was very slow and kept crashing so the only thing is, i didnt manage to get all 3 unzipped folders on there. would that make a difference?
edit: hope I can still work towards fixing it - i need to check if i have a compatible micro sd card reader when i get back from work! please keep any ideas coming
You need the DREAIMG.nbh on your sdcard. Download the DREAIMG-RC29.zip file, unzip, place DREAIMG.nbh in /sdcard, boot into bootloader, and flash.
i did what cloverdale described on a bricked G1 and it worked just fine , now i need to figure out how to get donut on the mobile
anybody? pm if you can help and TIA
cloverdale said:
You need the DREAIMG.nbh on your sdcard. Download the DREAIMG-RC29.zip file, unzip, place DREAIMG.nbh in /sdcard, boot into bootloader, and flash.
Click to expand...
Click to collapse
Thanks for your reply. I'm downloading this one DREAIMG-RC29.zip
I'll then extract on my computer, isolate the DREAIMG.nbh file and copy it into root of SD card.
Is that correct so far
How do I flash?
Many thanks
Hmm, been doing as much research as I can in the time I have, and it appears I need to type command prompts into the fastboot screen? If someone could tell me exactly what to do, that would be a lifesaver, because I am really missing my G1
I didn't think I was this much of a n00b, but apparently so, heh.
bump.. been doing as much research as possible, but most of my net access atm is from work which has many sides blocked (incl XDA!) and im not entirely sure how to do these things that have been suggested.. if someone could just go into a little bit more detail id be really grateful.
Tranquility__89 said:
Thanks for your reply. I'm downloading this one DREAIMG-RC29.zip
I'll then extract on my computer, isolate the DREAIMG.nbh file and copy it into root of SD card.
Is that correct so far
How do I flash?
Many thanks
Click to expand...
Click to collapse
Once you have extracted DREAIMG.nbh and placed it on the sdcard, all you need to do is power on while holding camera, and the installation should begin (or perhaps it asks you to confirm), and not console is needed. Let it do its work, and when it tells you to reboot, press and hold call+menu+end and you will reboot to RC29.
cloverdale said:
You need the DREAIMG.nbh on your sdcard. Download the DREAIMG-RC29.zip file, unzip, place DREAIMG.nbh in /sdcard, boot into bootloader, and flash.
Click to expand...
Click to collapse
And if that doesn't work I would see if your sdcard is fat32
Thanks guys!!!!!!!!!!! it worked! Much thanks indeed.
There is another problem now though, if anyone can help: I'm doing a manual update to 1.5 (rc8) from 1.0 (rc7) and its getting stuck on the G1 screen and not loading.. not hard bricked or anything, can still access recovery and bootloader.. This thread has more information: http://forum.xda-developers.com/showthread.php?t=625677
thanks again
help please
Hi, my g1 is stuck at the seria10 fastboot screen. It is a US g1 that I purchased rooted. I know enough about these sort of things to get myself into trouble. I removed an app (card game) and my phone then got stuck so I did a battery pull. Now all it will do is either spin on the g1 screen or I can get the three skateboards fastboot screen. I am unsure as to what to do now. I downloaded the rc29 build and put it onto my sd card. I am on a mac so I do not think I use FAT32. I thought putting the rc29 on my sd card and holding the power/send/menu key would tell the device to reboot with the rc29 build. Should I have deleted all the stuff of the sd card? I just want my phone to work - I didn't know the phone was rooted until after I had purchased it from a dude off craigslist. any help is appreciated.
sd card is formatted to fat 16 not 32 according to my diskimage. Help?
brian
bcp0809 said:
Hi, my g1 is stuck at the seria10 fastboot screen. It is a US g1 that I purchased rooted. I know enough about these sort of things to get myself into trouble. I removed an app (card game) and my phone then got stuck so I did a battery pull. Now all it will do is either spin on the g1 screen or I can get the three skateboards fastboot screen. I am unsure as to what to do now. I downloaded the rc29 build and put it onto my sd card. I am on a mac so I do not think I use FAT32. I thought putting the rc29 on my sd card and holding the power/send/menu key would tell the device to reboot with the rc29 build. Should I have deleted all the stuff of the sd card? I just want my phone to work - I didn't know the phone was rooted until after I had purchased it from a dude off craigslist. any help is appreciated.
sd card is formatted to fat 16 not 32 according to my diskimage. Help?
brian
Click to expand...
Click to collapse
Disk utility on a Mac will allow you to format to fat32, you must do this. What happens when you power on the phone while holding down home?
I was able to do the home power thing and wiped the handset then rebooted it. Not sure why it worked this time over any previous times...oh well at least it works. Thank you for your prompt reply.
Hi guys
So after unsuccessfully trying to root my G1, I changed my mind on the mastter and decided to keep it stock OS. I managed to get back to Android 1.0.
I’ve put a formatted and FAT32 SD card in the phone, with RC8 (UK phone) on it named update.zip (file ext hidden in windows).
I boot up the phone holding home key, ALT L then ALT S. It boots successfully saying things like ‘package verified’ etc until it says ‘install complete’. Then it says ‘press home+back to reboot your phone. When I do that it says ‘writing radio image’ then reboots. When it turns back on it has a picture of a sim card and an arrow or a phone and a box then reboots again. And here lies the problem: it never leaves the G1 screen (the first screen displayed when powering on the device. I’m able to power into recovery mode and fastboot mode, and from fastboot mode I can recover the phone by flashing to 1.0 via DREAIMG.NBH, but I really want to be running 1.6.
Can anyone help?
Many thanks
What phone are you using...a UK G1 or a US G1, as your trying to flash a UK rom...(rc8) have you tried flashing RC29? After flashing to android 1.0 it will prompt you to update your phone to 1.6 after that.
Tranquility__89 said:
Hi guys
So after unsuccessfully trying to root my G1, I changed my mind on the mastter and decided to keep it stock OS. I managed to get back to Android 1.0.
I’ve put a formatted and FAT32 SD card in the phone, with RC8 (UK phone) on it named update.zip (file ext hidden in windows).
I boot up the phone holding home key, ALT L then ALT S. It boots successfully saying things like ‘package verified’ etc until it says ‘install complete’. Then it says ‘press home+back to reboot your phone. When I do that it says ‘writing radio image’ then reboots. When it turns back on it has a picture of a sim card and an arrow or a phone and a box then reboots again. And here lies the problem: it never leaves the G1 screen (the first screen displayed when powering on the device. I’m able to power into recovery mode and fastboot mode, and from fastboot mode I can recover the phone by flashing to 1.0 via DREAIMG.NBH, but I really want to be running 1.6.
Can anyone help?
Many thanks
Click to expand...
Click to collapse
That's because you didn't flash your SPL yet.. I'll edit this post with the link to it. Oh and before I do, which rom are you trying to flash?
protomanez said:
What phone are you using...a UK G1 or a US G1, as your trying to flash a UK rom...(rc8) have you tried flashing RC29? After flashing to android 1.0 it will prompt you to update your phone to 1.6 after that.
Click to expand...
Click to collapse
Thanks for the suggestion protomanez - it's a UK G1.
xAbstract said:
That's because you didn't flash your SPL yet.. I'll edit this post with the link to it. Oh and before I do, which rom are you trying to flash?
Click to expand...
Click to collapse
That sounds promising I'm trying to flash UK 1.5 RC8. So I have to install this SPL first and then install the software? I'm correct in jumping straight from 1.0 to 1.5 right?
Tranquility__89 said:
That sounds promising I'm trying to flash UK 1.5 RC8. So I have to install this SPL first and then install the software? I'm correct in jumping straight from 1.0 to 1.5 right?
Click to expand...
Click to collapse
Do I need to flash this SPL? The bottom one on this page http://code.google.com/p/android-roms/downloads/list?q=label:SPL
it's called G1originalBootloadernocheck.zip or something similar
I wouldn't trust that, but I don't know just hold on. Wait a minute, so you flashed the RC8 rom? Are you sure, how long did you wait at the T-mobile G1 screen for? Try flashing RC8 again and let the phone do it's thing. Wait a max of 10 minutes for the phone to load.
Tranquility__89 said:
That sounds promising I'm trying to flash UK 1.5 RC8. So I have to install this SPL first and then install the software? I'm correct in jumping straight from 1.0 to 1.5 right?
Click to expand...
Click to collapse
I'm hoping that you're rooted at 1.0.. And nono, you flash radio first, then SPL THEN the rom.
xAbstract said:
I'm hoping that you're rooted at 1.0.. And nono, you flash radio first, then SPL THEN the rom.
Click to expand...
Click to collapse
He's trying to go back to stock, not flash a rom :U.
Tranquility__89 said:
That sounds promising I'm trying to flash UK 1.5 RC8. So I have to install this SPL first and then install the software? I'm correct in jumping straight from 1.0 to 1.5 right?
Click to expand...
Click to collapse
... sounds like he wants to flash.
-EDIT-
Why would he want to go back to stock if he flashed 1.0? Isn't that the first thing you do when you root?
After you flash DREAIMG.nbh, give the phone a few days and it will update over the air.
xAbstract said:
... sounds like he wants to flash.
-EDIT-
Why would he want to go back to stock if he flashed 1.0? Isn't that the first thing you do when you root?
Click to expand...
Click to collapse
He said he changed his mind because he tried to root but he failed so he's trying to go back to stock OS.
protomanez said:
He said he changed his mind because he tried to root but he failed so he's trying to go back to stock OS.
Click to expand...
Click to collapse
Oh my bad. My lack of attention span prevented me from reading that but to go back to the stock, do what cloverdale said. Reflash your G1 with the RC8 and WAIT for the update. There's no need to do it manually.
Thanks guys! Yes the root looked like it was about to brick my phone so I abandoned it and was feeling overwhelming relieved to even get normal OS back on my phone. So I should just wait for the over the air update (in the UK) and it will automatically bring it up to 1.6 again? Sorry for the late reply, my internet has only just started working, and itll be off again soon!
Why not do it manually btw guys?
Yeah you can just do what cloverdale said, or you can go to the settings(pick it by pressing menu on the phone) and scoll all the way to the bottom to "about phone" I believe there will be an "upgrade" option but I'm not quite sure . You can do it manually by dling the upgrade off the internet somewhere but it's probably better(on the safe side) to just download it from your phone.
Tranquility__89 said:
Thanks guys! Yes the root looked like it was about to brick my phone so I abandoned it and was feeling overwhelming relieved to even get normal OS back on my phone. So I should just wait for the over the air update (in the UK) and it will automatically bring it up to 1.6 again? Sorry for the late reply, my internet has only just started working, and itll be off again soon!
Why not do it manually btw guys?
Click to expand...
Click to collapse
Yes, just give it some time and it will update to 1.6 (or maybe 2.0/2.1). I would suggest waiting of the OTA update and not doing it manually simply because I what I read about your reactions to rooting. I am not trying to be mean when I say this, but the stress it seemed to cause from starting the rooting process may be recreated through a manual flash. Take life easy, relax, and it will update very soon.
OK, no offence taken. I didnt know 2.0 was out for the G1 yet..
I think my rooting went wrong because I didnt flash a radio image or SPL prior to the software - I tried to complete it with limited net access and therefore information, and a non working phone and non working internet is too much of a hinderance as i need these things every day.
I mainly wanted to root it to make the higher end 3d games run smoother via overclocking and use it as a wifi point so i could access the net properly again whilst BT stop ****ing around.