Unroot without flashing DREAIMG.nbh - G1 Q&A, Help & Troubleshooting

I have a particular issue in trying to unroot my G1. The battery meter for the phone (hardware) is saying low voltage (0% when booted) and will not charge a battery.
I have the original bootloader reinstalled. I have put the DREAIMG.nbh on the sdcard and tried flashing it at the rainbow screen. The problem here is, the phone says "Low voltage... replace battery... hit action key to continue" when booting (camera+power). Then goes back to the rainbow screen with "Serial0" displayed.
I cannot seem to get the DREAIMG.nbh to flash. Is their another way to unroot and get back to a stock image without the DREAIMG.nbh file?
I am sending the phone back to t-mobile for a replacement and even they didn't seem to be familiar with this power issue.
I apologize if this has been answered somewhere already but my searches did not turn up anything useful when not being able to use DREAIMG.nbh
Thanks for any help.
The phone was: Cyanogen 3.6.8.1 with Recovery 1.4, Apps2Sd

I cannot seem to get the DREAIMG.nbh to flash. Is their another way to unroot and get back to a stock image without the DREAIMG.nbh file?
Click to expand...
Click to collapse
I'm pretty sure that's not possible. Do you want to reflash to stock because you are worried about T-mobile yelling at you and denying your warranty?

DirectMatrix said:
I'm pretty sure that's not possible. Do you want to reflash to stock because you are worried about T-mobile yelling at you and denying your warranty?
Click to expand...
Click to collapse
LOL. I don't want T-Mobile yelling at me.

DirectMatrix said:
I'm pretty sure that's not possible. Do you want to reflash to stock because you are worried about T-mobile yelling at you and denying your warranty?
Click to expand...
Click to collapse
Exactly, since this seems like an unusual problem (from what I've gathered) I'm worried they might dig into the phone and deny the warranty... Guess I'll just have to get it back to as normal as I can then send it back.

i know for sure that the t-mo OTA update is somewhere on xda, as long as the phone is plugged in to the USB or another charger while you are flashing the OTA via the recovery screen then you shouldn't have a problem. you should be able to search the entire dream forum for "t-mo OTA URL" then you will find it. you will have to edit a file and resign the t-mo update and then flash it, but i am sure that recovery will allow you to flash even on a low battery

Have you tried flashing it with the the power cable plugged in? If its plugged in, it *might* not give you that warning about low battery as it has another source of steady power.

Related

UK G1 bricked after installing Shop savvy - help please

Hi guys,
UK G1 (Dream) phone recently updated to the 1.6 build, all working fine.
Yesterday I tried installing the free app Shop Savvy. the phone resetted itself after install and sat on the G1 boot screen permanently.
Now phone will pass this boot screen (Tmobile G1)
Tried:
Recovery mode - will not work at all
Quick boot - brings up the multicolour screen but does nothing after.
**PHONE IS NOT ROOTED**
looks like I have had the phone JUST over a year, not looking good...
Any ideas?
You can boot in to the SPL/bootloader so thankfully you haven't bricked
If you're on a contract with tmo you could take it back to the store and they should give you a replacement, but where's the fun in that?
If you want to fix the problem yourself, all you need to do is downgrade to firmware 1.1, then accept the OTA update to 1.6.
Here's the procedure:
1)Put the phones SD card in to a card reader and format as fat32
2) Extract this file and copy it to your SD card as 'DREAIMG.nbh'
3) Put the card back in the phone and hold down power and camera to boot in to the bootloader.
4) Flash it. (Action button is the trackball).
It's a good idea to leave the charger plugged in and have a decent amount of charge in the battery (eg 40%+).
Afterwards the phone will restart and you will need to re-enter your google account info. All your apps and data will be gone, but there's not much we can do about. You can set things up and install apps while you wait for the prompt to update.
Thanks alot AdrianK,
Really appreciate the steps and info, nice one
I have done some flashing on other phones etc so I have no problem with this. However, I am wondering how a normal app such as Shop Savvy could corrupt my ROM and am wondering if it might not be better to get a new phone as this one could have hardware fault?
What do you think?
Silver.
OK,
did exactly as you said Adrian. Phone went through all the flashing routine then, right at the end said press action button to continue (trackball) every time I press the trackball phone returns to the bootloader screen
What now?
SilverfoxUK said:
OK,
did exactly as you said Adrian. Phone went through all the flashing routine then, right at the end said press action button to continue (trackball) every time I press the trackball phone returns to the bootloader screen
What now?
Click to expand...
Click to collapse
I think you can take the battery out restart the phone
Thanks but unfortunately I have already tried that.
Phone just sits on the G1 boot screen as before...
Any other Ideas?
is that ROM you linked for me a UK ROM Adrian?
Once you get to RC7 use these to build back upto 1.6
http://code.google.com/p/official-android-firmware/downloads/list
SilverfoxUK said:
Thanks but unfortunately I have already tried that.
Phone just sits on the G1 boot screen as before...
Any other Ideas?
is that ROM you linked for me a UK ROM Adrian?
Click to expand...
Click to collapse
Yeah that's the RC7 ROM, the UK ROM for 1.1. RC29 is 1.1 for US phones.
This is all very odd, especially that it was an app that caused it, or as you suggested possible hardward failure. Oh well, I guess all you can do now is take it back to tmo.

Help help help root problem

OK this is the deal, i bought a phone off someone from craigslist. i have no idea what this person has done on the phone it came as stock donut. no root or anything of the sort. and there is no way to contact the person to ask what or if they tried to do anything. i have been trying every which way and yes the search bar is my friend. and nothing. ive done this before MULTIPLE times i am not new to rooting and flashing. Everytime ive tried to load something it always says no signature(#), number sign for random file numbers, i have tried to downgrade everything spl, radio and down to rc29, and trying to figure out if i could downgrade the recovery to the original recovery not the 2 (e). ive stumbled upon the idea that i might be missing files. maybe the otacerts i believe. i searched that also and found someone only saying to reinstall rc29 THATS MY PROBLEM I CANT IT WONT LET ME. Please someone help before i bust my head open on my desk.
and sorry about the punctuation typing super fast and avoiding my boss.
No signature usually means the update isnt signed.... and you probably got the update.zip thats corrupt...
Ive tried 3 different downloads of every file aka different dev for each thing. Anything i try and put as Update or even left as Original such as the .nbh it all comes up no sig. is everything online corrupt?
You don't have a root hence no luck on roms.
.nbh is not flashed thru recovery. Put it on your sd, power down your phone and power up holding power and camera buttons. Phone should find DREAIMG.nbh and restore your device to RC29. From there, secure your root and it's business as usual. Good luck.
borodin1 said:
You don't have a root hence no luck on roms.
.nbh is not flashed thru recovery. Put it on your sd, power down your phone and power up holding power and camera buttons. Phone should find DREAIMG.nbh and restore your device to RC29. From there, secure your root and it's business as usual. Good luck.
Click to expand...
Click to collapse
going to try this again

After manual update: stuck on G1 screen after update file – help!

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.

need help dead phone

I was attempting to flash the ICS4 ROM. I had formatted /system and was done with installing the from from zip. Before I could do anything else, the phone just stopped being responsive. I pulled and restored the battery but the phone will not boot up. What to do now, short of going to my VZW store?
When you say it doesnt boot.. what exactly do you mean? Does anything come up on the screen?
nothing comes when you press the power button, screen remains blank.
ronaldheld said:
nothing comes when you press the power button, screen remains blank.
Click to expand...
Click to collapse
Did you try booting up into recovery and then going to fastboot and reinstalling the stock fxz file to see if that fixed it?
Sure the battery didn't die also?
The phone does not boot into recovery. Pressing the power button does nothing at all, as far as I can see.
I found out that the phone is literally fried. Whether the ICS4 ROM contributed is unknown.
You are most likely covered under manufacturer warranty - seems like a hardware failure. Never known of a ROM flash to fry a phone's board.
They also most likely won't know you even tried to flash a custom ROM.
That part is very good to know.
I will have restart again with rooting, and proceed with flashing Eclipse 2.2.
Is the place you live in very statically charged? When you touch metal do you get shocked alot?
If you touched the battery ports it could have discharged into the phones board and killed it.
Let us know what they do for you.
ronaldheld said:
That part is very good to know.
I will have restart again with rooting, and proceed with flashing Eclipse 2.2.
Click to expand...
Click to collapse
Compared to everything else we do here at XDA, the process to get rooted and flash a ROM is very basic. Getting the phone back up and running is the more difficult part.
What I can say to try is attempt to use a different battery. I had a problem once where both of my batteries functioned properly because I was able to test them in other phones. But when I placed that specific battery into my phone, it wouldn't boot up. I ended up using a different battery and was then able to boot into AP Fastboot and fxz to fix it. Then my "dysfunctional" battery worked properly again.

[Q] Please help me, is my phone bricked?

I'm a complete noob in dire need of help. I wanted to root my phone, and read the 3 procedures mentioned in the sticky thread. The 2nd one (nvflash) seemed very well explained and was sure to work with 2.3.4 so I decided to use that. As I was in my friend's house I used his pc and installed the drivers while my phone was connected in apx mode. Then I double clicked the "install internal xp" batch file which resulted in a black window with some texts, but seeing this my friend freaked out and closed the window before the process was finished. I told him he shouldn't have done that. I then disconnected the phone and switched it on. It seemed to switch on properly. So I then switched it off again and pressed and held the power and vol down switches to see if I got cwm. This showed LG screen for a few seconds and then the screen went off.
Now whatever I try to do I can only see the LG screen for a few seconds and then the screens goes off. No power on, no recovery, no nothing. And I can only attempt to even power on once, after the screen goes off I must remove the battery before the power button does anything again.
I tried to freshly nvflashing the recovery many times, but it made no difference. Does this mean my phone is bricked? Please tell me how I can solve this as I'm really worried.
NVFlashing the recovery again *should* have worked. So we first need to make sure you're trying to start CWM the correct way.
1) Unplug phone
2) Remove battery for 10 seconds.
3) Insert battery
4) Hold volume-down, do not let go, keep pressing it.
5) Press power button, keep it pressed.
If/when you get the second LG-logo, bluish halo, you can release both buttons, not before.
Nope, that was exactly what I was doing to access the recovery. I tried it again just now and it didn't work.
It just displayed the regular LG logo and then the screen went off. I'm not sure the phone completely shuts down 'cause if I keep it like that it gets quite hot and I can't use the power button again to try to power up. Only removing and re-inserting the battery gives me another attempt.
Is there any chance this is a hardware issue?
Hardly any chance this is hardware related if it was working before the first NVFlash.
Good, next step will be to NVFlash a complete stock ROM. You will unfortunately lose any data you might have on it, but that's the price to pay.
Go here, follow the instructions precisely, skip installation of apx-driver. Report back.
http://www.modaco.com/topic/335474-25-mar-nvflash-stock-rom-release-v10b-dated-1300166062-15032011/
Ok, so I just download the 200mb file, connect in apx mode and double click flash.bat, right? And will this rom work regardless of country/region? I'm from India and was running stock 2.3.4 with v20* (can't remember the letter. God, I hate myself).
sean8000 said:
Ok, so I just download the 200mb file, connect in apx mode and double click flash.bat, right? And will this rom work regardless of country/region? I'm from India and was running stock 2.3.4 with v20* (can't remember the letter. God, I hate myself).
Click to expand...
Click to collapse
It works, yes, but is the original Froyo. This is just a way to get the phone up and running again.
Later you have a few choices. Either install CWM, then install you ROM of choice, or upgrade it to the latest for your region by using the LG Update tool.
EDIT. Oh, and btw, it is better to open a command-window and type the flash.bat command. If there are any errors you will still have them on-screen.
Thank you for all the help and support. I didn't get a chance to flash the rom till now (being on a vacation without a smartphone sucks). But I'll try it asap and report back.
So, how did it go?
TrymHansen said:
So, how did it go?
Click to expand...
Click to collapse
I haven't flashed it yet. I've decided to do it after I return home. I'm at my friend's house for 2 more days.
Ok, bad news. I flashed the stock rom you linked. The process went pretty smoothly. After the window got closed and the lg logo on the phone was visible 2 times, I unplugged it and installed the battery. But switching it on wasn't fruitful. It just displayed the LG logo for a couple of seconds and then the screen went off (just like before, only faster). I tried repeating the whole process, even tried to nvflash cwm once again, but nothing happened.
So is it a hardware issue? My phone is no longer in warranty period, so a hardware problem would be really bad...
So is it a hardware issue?
Click to expand...
Click to collapse
I don't know.
What would be helpful is to get a copy of the output you get when you NVFlash, it's simply the only way to verify that the flash process went ok. If you have an aborted flash it of course won't work, and may display the behaviour you describe.
EDIT: Btw, early on there were some ROMs which refused to boot properly unless the baseband was of an early variety as well.
If you feel confident the NVFlash has been successfull, smartflash an old baseband as well, see if it boots then.
Its hardly a hardware problem. As you dont have the warranty anymore, and the bootloader is probably corrupted, i would recommend a Jtag service.
Please, dont be afraid of hitting thanks
gabriel2anjos said:
Its hardly a hardware problem. As you dont have the warranty anymore, and the bootloader is probably corrupted, i would recommend a Jtag service.
Please, dont be afraid of hitting thanks
Click to expand...
Click to collapse
Now what's this "Jtag service"? (edit- I googled it and it seems to be a method of un-bricking stuff with specialized hardware or something, but I'm not sure I can have that done where I live)
Is there any way to fix the bootloader by myself?
@Trym- So, I should download a v10 baseband and flash it with this "smartflash" tool, right?
sean8000 said:
@Trym- So, I should download a v10 baseband and flash it with this "smartflash" tool, right?
Click to expand...
Click to collapse
Yeah, as a last-ditch effort. I haven't the slightest hope it'll help, but it can't hurt to try.
TrymHansen said:
Yeah, as a last-ditch effort. I haven't the slightest hope it'll help, but it can't hurt to try.
Click to expand...
Click to collapse
Ok, I'll try that when I have the time.
So do you know anything about this corrupted bootloader thing? Does this mean my phone's hard bricked?
sean8000 said:
So do you know anything about this corrupted bootloader thing? Does this mean my phone's hard bricked?
Click to expand...
Click to collapse
If it is you're only the second person in this forum to ever brick his phone. Anything's possible I guess. Some flash cells may have been damaged the first time the power was yanked. But then we should presumably get some verification errors during flashing.
Anyway, I'm at my wits end, and I really do hope you get it up and running, but I don't have anything more to contribute. Good luck.
Corrupted bootloader means that your cellphone simply don't know what to do when you hit the power button, due to the damage. As the cell phone can't turn, the pc can't recognize it. If your cell phone were a samsung, you could try to use a jig to have acesso to the download mode. But I don't know if it would work for a LG. You could try anyway.
And if you live at big city, usually it's common to have some jtag services.
Please, dont be afraid of hitting thanks
Please, dont be afraid of hitting thanks
Ok, so I took the phone to the service center today. The guys there said its battery terminals are messed up. They said replacement terminals are not easily available, but they'll try to find some. And of course I'll have to pay for it. I guess it's still better than using the phone as a paperweight.
What do you guys think?
Good luck I managed to mess up my phone like you too. I'm from India. But the difference was that I was covered by warranty. I managed to get a bunch of hardware replaced and was up and running again.

Categories

Resources