Database Develop

US G1 on EU wont boot and wont recover

Hello everyone,
i really thank all the people who are investing lots of time on this site to help others. I have found myself many solutions to many issues in many of my phones.
now i have a new issue and I have not benn able to find a solution. maybe its hidden in the forums, if you know it, please send my a link.
issue:
got a g1 from the US, using it in EU.
if I turn it on, shows the G1 logo folowed by the recovery(android system recovery uitility)
It doesnt matter if I do something else, it allways comes the screen.
Tried several upgrades but it allways tells me:
Install form sdcard...
Finding...
Opening...
Verifying...
E:No signature (XXX files)
E:Verification failed
Installation aborted.
on top of the recovery there is a message:
E: can't open /cache/recovery/command --> to this i found several solutions, but all require a running g1... this is not the case.
Also the "back+power" wont load the defaults, it doesnt matter what i do.. wont do anything.
PS: SD is an 8Gb class 6 which was working on my old G1, fresh formated
any clues?
most appreciated!
Luis

I almost forgot to mention..
Power + Cam, fastloader wont work, wont load.. also found a solution having a working G1.. again.. this is not the case. I got the phone yesterday and should be working, it looks rather soft-bricked

A hint might be to post this in the Dream Q & A Section before you get battered for posting in the Dev section....

many thanks! Q&A should have been!
any ideas to solve my problem? thanks

E:No signature (XXX files)
E:Verification failed
is due to the ROM not being signed.
if you want to get into bootloader to flash nandroid backups
use
adb reboot bootloader
Click to expand...
Click to collapse

Hi B-man007,
thanks.. is there a way to use ADB if the phone has no OS? and if its not recognized by PC... ? found solutions about how to use it.. IF the phone is running. please let me know if i am missing something here. cheers!
any other solutions?

if the roms that i tried are not signed.. could you suggest me one which is?
tried from original ones to cooked.. same responce. i even tried 30 to 33.. to see waht happens, it started but showed me again an error message, it would make sense if the installed rom would have been 30. i was just trying around.
any links to a very old android which is signed? to keep on trying.. cheers!

Since you have a US G1, flash the RC29 DREAIMG.nbh to get to Android 1.0
ADB can be used in recovery since there is a kernel being used. You need to install the drivers for it to work

no cannt do.. driver for win7 x64 are not te be found and the update from RC29 not possible. i cannt access the booloader to install images ;(
tried several signed updates and roms, allways the same crap!
any other idea? thanks!

The adb drivers for vista x64 should work just fine. If you can't get into bootloader by holding Cam+Power
you will need adb to actually boot into the bootloader to flash the RC image

so.. many tests .. same situation
ADB works if the device is conected. it could be recognized if the bootload is on OR if android is running.
none of this works for me.
i cannt access anything but the android recovery, believe that the old user saved recovery on SDcard and send me the phone w/o it... E:/can't access recovery.. blah
i am getting really angry with the phone and the seller.. damm eVay

"DLL LOAD FAIL" Galaxy TAB problem in updating firmware !

Hello all,
this problem frustrates the hell outta me, now i have been informed by Kies that a new firmware is there for Gtab...but...i start updating, then the mesage "DLL LOAD FAIL" appears, whilst the Gtab is displaying a yellow "android robot" doing some cleaning and stuff...
My code is an XSG one, and i cannot seem to update at all...please help, as i have searched alot here in the forums, but could'nt find any (unless i missed, of course).
ow, i read about the odin way of updating, but i still could'nt get a solid guide on how to do it...would appreciate anyone to shed some light on it too...if possible..
thanks

anyone please ???????

you should be able to find all kinds of info on Odin. last thing I read on Odin that should help is the little how to guide that is posted with the Gingerbread OverCome ROM. go take a look at it inthe Development section.

thanks, but, does languages gets affected by the odin method ?
my gtab is localized to have arabic on it, if i do any odin will it be gone ? It seems odin is the only option i have since samsung kies itself seems faulty, and refuses to work with this DLL LOAD FAIL kinda thing.
shall i proceed ?
EDIT: now i figured out another new error: unzip error...so i installed winrar, and, the update completed ! However, i only received a minor update for the current froyo firmware, there were no gingerbread for me (code XSG)...whats that supposed to mean ??

I have no idea about locality. i would imagine the important thing is the actual ROM you are flashing. Odin just loads what you give it. Proceed at your own risk. if you are nervous, wait a few days until there is more feedback available from the community.

[Q] SGS i9000 Operating System Problem

Hi guys,
I just got given an SGS i9000 that was on Bell Canada (not sure if that's relevant!?) and I wanted to root and load a custom rom etc, I downloaded odin and placed the 3 files in their relevant places and started the process, now the SGS won't boot and gives the following message:
E:failed to mount /dbdata (Invalid argument)
and also:
Installing Milti-CSC...
Can't access to ''/system/csc/BMC/system/'
Does anyone know how I can fix this? I've tried going back through odin, but the SGS is no longer recognised on any of my computers :crying:
Any help/pointers would be awesome!!

jesper10 said:
Hi guys,
I just got given an SGS i9000 that was on Bell Canada (not sure if that's relevant!?) and I wanted to root and load a custom rom etc, I downloaded odin and placed the 3 files in their relevant places and started the process, now the SGS won't boot and gives the following message:
E:failed to mount /dbdata (Invalid argument)
and also:
Installing Milti-CSC...
Can't access to ''/system/csc/BMC/system/'
Does anyone know how I can fix this? I've tried going back through odin, but the SGS is no longer recognised on any of my computers :crying:
Any help/pointers would be awesome!!
Click to expand...
Click to collapse
you need to download odin then you flash dbdata.rfs.tar in though odin to the sgs in recovery mode.files below. maybe this will help.

jesper10 said:
Hi guys,
I just got given an SGS i9000 that was on Bell Canada (not sure if that's relevant!?) and I wanted to root and load a custom rom etc, I downloaded odin and placed the 3 files in their relevant places and started the process, now the SGS won't boot and gives the following message:
E:failed to mount /dbdata (Invalid argument)
and also:
Installing Milti-CSC...
Can't access to ''/system/csc/BMC/system/'
Does anyone know how I can fix this? I've tried going back through odin, but the SGS is no longer recognised on any of my computers :crying:
Any help/pointers would be awesome!!
Click to expand...
Click to collapse
1. Just do a 'wipe data/factory reset' and reboot the device when done.
2. Let the device boot all the way then turn it off.
3. Re-enter Download Mode and re-flash only the CSC file without pit and without re-partition...

Hi guys!
Thank you for the replies and taking the time to help...my biggest problem is getting the computer to recognise the phone, I think when I flashed whatever it was before I've somehow "deleted" the O/S on the phone and now no mater what PC I plug it into the phone never gets recognised...and that means I can't use odin
If I can get that bit fixed, then I think I can recover the phone but just don't know how to fix that...odin was working perfectly before so I know it does, just need the PC to find the phone now!
Any thoughts? I've tried re-downloading Kies/drivers etc but to no avail.

But you can enter Download Mode?

That's probably has something to do with the fact that you have a I9000M, which is the Canada Bell version of the I9000. There are some subtle hardware differences between the two. Honestly, **** Samsung and their variants. It's a pain in the *** trying to remember if the difference still matters any more. When the I9000M first came out we encountered a whole load of issues with people frying their memories and having to send it back to Samsung for replacement. I think someone eventually came up with a way to overcome this, but I didn't read much about it.
Anyway, try getting a stock I9000M rom instead and flash that. As for your PC not recognising it, you did reboot between uninstalling and reinstalling the Samsung drivers right? Also, kies must NOT be running in the background when you use odin, otherwise odin will not recognise your phone.

KUN1 said:
But you can enter Download Mode?
Click to expand...
Click to collapse
Yeah, I can get into download mode but nothing happens from there...because the laptops/PC won't recognise the phone I can't transfer anything on to it!
I've tried installing a rom from SD card but it fails :crying:
Any thoughts?

snapper.fishes said:
That's probably has something to do with the fact that you have a I9000M, which is the Canada Bell version of the I9000. There are some subtle hardware differences between the two. Honestly, **** Samsung and their variants. It's a pain in the *** trying to remember if the difference still matters any more. When the I9000M first came out we encountered a whole load of issues with people frying their memories and having to send it back to Samsung for replacement. I think someone eventually came up with a way to overcome this, but I didn't read much about it.
Anyway, try getting a stock I9000M rom instead and flash that. As for your PC not recognising it, you did reboot between uninstalling and reinstalling the Samsung drivers right? Also, kies must NOT be running in the background when you use odin, otherwise odin will not recognise your phone.
Click to expand...
Click to collapse
Yeah, I read about that actually - I should maybe have paid more attention when I was looking into this in the first place!
Thanks for your reply man, I'm going to try getting stock I9000M rom tonight and have a go with that! But yeah, 3 different PCs/laptops I've tried it on, with variations of with/without Kies...still no joy as yet!
Thanks again for the reply though :good:

[Q] Aoson M19 Bricked TAB

Please help out I have a AOSON M19 Bricked TAB,
I tried to recover the TAB to factory settings, It gone bad during recovery.
when I tried to connect using RKAndroidTool 1.35 It shows the tab like Found RKAndroid Maskrom Rock UBS, but giving error while updating the Image. I found the stock ROM 4.0 update.
I also Tried RKBatch Tool.
I have opened the TAB tried Shorting 7n8 pin on NAND chip tried to boot but failed,
in the PC it is showing RK30 Device but in RKBatch tool it is showing RK29
I have googled everything not able to found solution
Kindly anyone help out its my customer's TAB as I am unable to answer Him

sathvik1 said:
Please help out I have a AOSON M19 Bricked TAB,
I tried to recover the TAB to factory settings, It gone bad during recovery.
when I tried to connect using RKAndroidTool 1.35 It shows the tab like Found RKAndroid Maskrom Rock UBS, but giving error while updating the Image. I found the stock ROM 4.0 update.
I also Tried RKBatch Tool.
I have opened the TAB tried Shorting 7n8 pin on NAND chip tried to boot but failed,
in the PC it is showing RK30 Device but in RKBatch tool it is showing RK29
I have googled everything not able to found solution
Kindly anyone help out its my customer's TAB as I am unable to answer Him
Click to expand...
Click to collapse
I believe that the bootloader partition is corrupted....No way to help that...Try to JTAG it...

BlackSoulxxx said:
I believe that the bootloader partition is corrupted....No way to help that...Try to JTAG it...
Click to expand...
Click to collapse
Dear Fried
Can you please briefly explain what is JTAG
and how can I try it????

sathvik1 said:
Dear Fried
Can you please briefly explain what is JTAG
and how can I try it????
Click to expand...
Click to collapse
Since you are not familiar with it...http://en.wikipedia.org/wiki/Joint_Test_Action_Group
Buy some tool to JTAG eMMC...

Bricked my AT&T Samsung Galaxy S4 Active i537. Advice?

I attempted going to my recovery mode and found a message saying "System software not authorized by AT&T has been detected on your phone." When you pay attention to the top left of Odin mode when you attempt to install, two red text lines appear. The first being "START [224, 1440]" and the next being "SECURE CHECK FAIL : recovery" I assume this is because AT&T detected something that was not supposed to be there.
The reason I believe AT&T detected something was because I attempted to flash a rom for Android 4.4.2 (Lollipop) using Droidviews tutorial (sorry, new user so I can't post the link :/) among others. This was with root access, which may have tripped the bootloader as well. I believe I was supposed to install a custom bootloader like TWRP or CWM beforehand (and I tried getting TWRP but it did not seem possible with AT&T's bootloader so I figured I may as well try it without and afterwards it would be easier); however, I never read any instructions in any of the websites I have used to root/update my phone that say I must have it so I am skeptical. Any guesses on how to fix it?

I also tried to flash the stock rom via Odin. Maybe it didn't have the "official" AT&T signature on it because I got the same error, but I looked anywhere I thought there may be a stock rom that would work. Any suggestions would be appreciated

Raeffion said:
I also tried to flash the stock rom via Odin. Maybe it didn't have the "official" AT&T signature on it because I got the same error, but I looked anywhere I thought there may be a stock rom that would work. Any suggestions would be appreciated
Click to expand...
Click to collapse
Take a look at the stickies.
http://forum.xda-developers.com/galaxy-s4-active/general/galaxy-s4-active-firmware-guide-t2892445

Devo7v said:
Take a look at the stickies.
http://forum.xda-developers.com/galaxy-s4-active/general/galaxy-s4-active-firmware-guide-t2892445
Click to expand...
Click to collapse
Well that certainly helped, I never knew someone created an Odin exe for the stock rom. It seemed to be working up until the end but for some reason it stopped (I forgot to log why as I am still a newb at this; I think it tripped my recovery mode again). I rebooted it and an error appeared saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." This seemed simple enough until Kies just would not connect to my phone. I left it for about 10 minutes until an error appeared saying that my device is not responding. It told me to reboot it and try again, so that's what I did. It seems to be doing the same thing regardless. I tried troubleshooting a connection error and it reinstalled the Kies drivers (I did this countless times), but the same thing kept happening.

Raeffion said:
Well that certainly helped, I never knew someone created an Odin exe for the stock rom. It seemed to be working up until the end but for some reason it stopped (I forgot to log why as I am still a newb at this; I think it tripped my recovery mode again). I rebooted it and an error appeared saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." This seemed simple enough until Kies just would not connect to my phone. I left it for about 10 minutes until an error appeared saying that my device is not responding. It told me to reboot it and try again, so that's what I did. It seems to be doing the same thing regardless. I tried troubleshooting a connection error and it reinstalled the Kies drivers (I did this countless times), but the same thing kept happening.
Click to expand...
Click to collapse
The one click seems to work well, but it never finishes completely. I cannot flash an OTA file as my bootloader is inaccessible. I may be able to do so from my computer but I have found no programs or guides to. Also, almost all of the downloads are down or outdated on the sticky with the exception of the ones I can't use.

Found the proper files to flash my phone successfully, the stickies were all outdated.