stuck at flashing adriod after downgrading to rc29 - G1 Android Development

long story short. i bought a locked g1. did the factory reset. dont have data but have a sim card. i was trying to do the activation over wifi.
when i press enter type reboot and press enter nothing happens.
every time i downgrade to rc29 everything goes smoothly, until its time to reset it after its complete. I restart it and it always get stuck at the screen with the andriod and it says andriod beside it flashing from time to time.
the only way around this is to next install cupcake which brings me back to the activations screen. but i still cant reboot by typing in reboot
its not taking any commands so i cant never get adb to work.
from my searches I'm the only that has this problem right after downgrading to rc29
any info/ help would be greatly appreciated

Do you mean the screen that says "touch the android to continue"? You might want to do what it says.
Oh, and you might want to also do what this FORUM says... post your questions in the QUESTIONS section.
It appears to me that there is nothing wrong except that you aren't willing to follow the instructions.
prelude91sit said:
long story short. i bought a locked g1. did the factory reset. dont have data but have a sim card. i was trying to do the activation over wifi.
when i press enter type reboot and press enter nothing happens.
every time i downgrade to rc29 everything goes smoothly, until its time to reset it after its complete. I restart it and it always get stuck at the screen with the andriod and it says andriod beside it.
the only way around this is to next install cupcake which brings me back to the activations screen. but i still cant reboot by typing in reboot
its not taking any commands so i cant never get adb to work.
from my searches I'm the only that has this problem right after downgrading to rc29
any info/ help would be greatly appreciated
Click to expand...
Click to collapse

If thats what i meant thats what I would have typed.
lbcoder said:
Do you mean the screen that says "touch the android to continue"? You might want to do what it says.
Oh, and you might want to also do what this FORUM says... post your questions in the QUESTIONS section.
It appears to me that there is nothing wrong except that you aren't willing to follow the instructions blah blah blah.
Click to expand...
Click to collapse

I only found one other person that was having this problem after loading dreaing.nbh and no solution was posted other than he might need to upgrade to rc33

prelude91sit said:
I only found one other person that was having this problem after loading dreaing.nbh and no solution was posted other than he might need to upgrade to rc33
Click to expand...
Click to collapse
You mean you found one other person who couldn't follow directions. You won't get anywhere by sassing lbcoder.
Start by posting the question in the right subforum, then follow the directions on the CM wiki.

Ive tried everything. I followed the directions to the T. Its not rocket science. I done everything over 10 times and still hangs at the flashing andriod boot screen. Never goes to the activation screen. I can do the <enter>reboot<enter> and that works. also was able to sucessfully connect to adb for the first. when i tried it at this screen. i get an error when trying to pull up the wifi settings cause my phone itsnt functioning properly.
anybody???

Maybe try something else like RC7. When I was rooting my G1 I followed a tutorial which was recommending RC7 and RC29 to do telnet stuff. RC7 wasn't working for me so I tried RC29 and everything was OK. Maybe it's the same for you, but in reversed order .

i well try it asap. the only reason i havent tried it yet cause im in the u.s. i didnt think i could use it.

got a not allowed. its funny cause when i first tried it i think the image was messed up. it said not found or something. try it a couple times didnt work stopped and let it power up normal and it worked. i was excited. i was able to register it over wifi and everything.. turned it off swiped sim cards ect. then it just got stuck back on the flashing andriod screen. wtf? so im starting all over again it hangs again at that screen as usual

i would try flashing RC33 first...

I would try posting this in the proper forum. It seems to me you asked a question, however you posted in the Android Development forum, see where I'm going with this?

Related

I've RESEARCHED, and found no answers. I think it's bricked

Hello to all, I am a noob here and have tried to adhere to all of the demands to do research and not post ?'s, but I am at a wall.
I have a Tilt and I ran the sim unlock and I was using the Sleuth 3.0 on it. Everything was working fine. I added the Iunlock cab and it worked fine as well. I then tried to install the icontacts, but i would have to go to program files and icontacts file in order to use I contacts. Well, wanna be innovative me thinks to try and move that file so it would replace something. I copied it to the windows appbuttons folder and deleted the regular contacts and nothing happened, then I put it in the start up folder and no luck, then I simply copied it to the windows folder not at the bottom where all of the extra files are. After that I tried to reset it and now all that I get is the bootloader screen. it reads as follows:
KAIS1*0 MFG
SPL-1.0.Olipof
CPLD-8
At the bottom, it shows either USB or Serial depending on if the usb is plugges up.
I tried running the sim unlock again and the dutty rom and both load to 100% but it goes back to the same screen. Any help would be greatly appreciated. Please help and thank you so much.
barrnunn said:
Hello to all, I am a noob here and have tried to adhere to all of the demands to do research and not post ?'s, but I am at a wall.
I have a Tilt and I ran the sim unlock and I was using the Sleuth 3.0 on it. Everything was working fine. I added the Iunlock cab and it worked fine as well. I then tried to install the icontacts, but i would have to go to program files and icontacts file in order to use I contacts. Well, wanna be innovative me thinks to try and move that file so it would replace something. I copied it to the windows appbuttons folder and deleted the regular contacts and nothing happened, then I put it in the start up folder and no luck, then I simply copied it to the windows folder not at the bottom where all of the extra files are. After that I tried to reset it and now all that I get is the bootloader screen. it reads as follows:
KAIS1*0 MFG
SPL-1.0.Olipof
CPLD-8
At the bottom, it shows either USB or Serial depending on if the usb is plugges up.
I tried running the sim unlock again and the dutty rom and both load to 100% but it goes back to the same screen. Any help would be greatly appreciated. Please help and thank you so much.
Click to expand...
Click to collapse
You could hard reset if you altered something in WM to cause it not to boot...hopefully
I tried the hard reset and same thing I flashes for a very split second loading and then goes back to the screen.
Hard reset is both item buttons above IE and Mail with soft reset correct?
barrnunn said:
I tried the hard reset and same thing I flashes for a very split second loading and then goes back to the screen.
Hard reset is both item buttons above IE and Mail with soft reset correct?
Click to expand...
Click to collapse
Yeah and then you press send...
- well you could try go into the bootloader and flash an OEM original ROM on i do not believe that doing this would brick your kaiser.
zeezee said:
You could hard reset if you altered something in WM to cause it not to boot...hopefully
Click to expand...
Click to collapse
In case u dont know how to do it:
http://wiki.xda-developers.com/index.php?pagename=Kaiser_Resets
Or else search for MTTY. That helped a lot of ppl who got stuck in boot loader.
barrnunn said:
I tried the hard reset and same thing I flashes for a very split second loading and then goes back to the screen.
Hard reset is both item buttons above IE and Mail with soft reset correct?
Click to expand...
Click to collapse
U need to hold the stylus in the hole longer, untl a message pops up on the page.
If it does not hardreset or help u, do what zeezee told u - flash a new rom.
OK, thank you all for you diligent assistance. I have tried the hard reset and it does the same thing...goes to black for about 2 seconds, then for a very split second goes to a grey screen and flashes loading then back to the bootloader.
I will try a search for the people stuck in bootloader and try flashing a OEM ROM, I will let you know how it goes. Thanks again.
barrnunn said:
OK, thank you all for you diligent assistance. I have tried the hard reset and it does the same thing...goes to black for about 2 seconds, then for a very split second goes to a grey screen and flashes loading then back to the bootloader.
I will try a search for the people stuck in bootloader and try flashing a OEM ROM, I will let you know how it goes. Thanks again.
Click to expand...
Click to collapse
Here is a list of OEM ROMs:http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
I do not see any Mods here around or somebody yelling (search button is your friend,search the wiki everything is there, bla bla)To having a woman at home change everything.. Thanks..!
Before you try the dangerous MTTY method, you could try refresh a oem rom w/ the SD method
ok, I am flashing an OEM rom now, but what does it mean to do it with the sd method?
barrnunn said:
ok, I am flashing an OEM rom now, but what does it mean to do it with the sd method?
Click to expand...
Click to collapse
From youre sd card (memorycard), look it up in wiki. Moust of us flashaholics keeps oure rom on oure memorycard and just rename the rom/bootsplash/radio or whateva and place it in root then activate bootloader -> flash. This is an alternative for not using usb cable, pc and active sync
http://wiki.xda-developers.com/index.php?pagename=KaiserSDFlash
ok thanks, but am i correct in understanding that to do that I have to use the phone to access the mem card?
My issue is that the only screen I get is bootloader, no nothing else. I can't even turn it off. I can take the battery out to get a black screen, but any action to try something will take it back to the bootloader screen. But for some reason, it still allows me to flash the ROM, I think. I flash it on my pc and then my phone goes to the grey screen where it shows the % of progress. It reaches 100% and the pc tells me to click finished and I do then it goes back to the bootloader.
barrnunn said:
ok thanks, but am i correct in understanding that to do that I have to use the phone to access the mem card?
My issue is that the only screen I get is bootloader, no nothing else. I can't even turn it off. I can take the battery out to get a black screen, but any action to try something will take it back to the bootloader screen. But for some reason, it still allows me to flash the ROM, I think. I flash it on my pc and then my phone goes to the grey screen where it shows the % of progress. It reaches 100% and the pc tells me to click finished and I do then it goes back to the bootloader.
Click to expand...
Click to collapse
put the rom image file on storage card and than power on phone in bootloader. the process will start automatically.
thesire said:
put the rom image file on storage card and than power on phone in bootloader. the process will start automatically.
Click to expand...
Click to collapse
yes, just use a card adapter or something to acess youre card (if you cant connect via active sync) then copy the rom over and follow the steps in wiki. Beeing stuck in the bootloader some times aint the worse place to be stuck
korakesion said:
I do not see any Mods here around or somebody yelling (search button is your friend,search the wiki everything is there, bla bla)To having a woman at home change everything.. Thanks..!
Click to expand...
Click to collapse
I don't mean to argue with you here and you are right about research threads, but honestly it's easy to get caught up in frustration with the amount of information. Some authors are good at documentation and some skip steps along the way or extra links are in the threads.
I just switched over to Gullum's Diamond Rom and was I nervous upgrading "Yes" and did I read much that I could "Yes". Were the instructions to HardSPL, Jump were a little unclear "Yes" so people asking questions are legit to a degree but we shouldn't also be eagar to pounce on...
tvos
tvos said:
I don't mean to argue with you here and you are right about research threads, but honestly it's easy to get caught up in frustration with the amount of information. Some authors are good at documentation and some skip steps along the way or extra links are in the threads.
I just switched over to Gullum's Diamond Rom and was I nervous upgrading "Yes" and did I read much that I could "Yes". Were the instructions to HardSPL, Jump were a little unclear "Yes" so people asking questions are legit to a degree but we shouldn't also be eagar to pounce on...
tvos
Click to expand...
Click to collapse
I agree with some of your remarks. Yes myself and others have jumped down people's throats yelling, "Search." One thing you have to remember though this is a developers forum, not a novice forum to help people making there phone look "cool."
Going into flashing / upgrading / modifying, you have to have a little bit of knowledge or time using Windows Mobile / Windows in General devices and machines.
Usually reading some background information can be a world a difference before jumping into this sort of thing.
I found the problem to stuck in bootloader. Thanks to all who have posted threads.
Originally Posted by GSLEON3
Many of you have noticed that in the past I spent a great deal of time helping people with Kaiser issues. Many of you have asked for help in the last few days & are probably feeling ignored. I am just unavailable at this time. My little sister had a Kidney Transplant operation on June 30th, 2008 & I have been spending much time traveling back & forth between my home in California & her's in Arizona. There were a few complications, but she is now doing well & recovering. I will be spending this weekend & most of next week helping to care for her & will be unavailable still for the next ten days or so.
There are many capable people in the Kaiser forum that will help. If you have hit a wall, be patient & I will begin to answer my PM's in the order they were recieved within the next week. Sorry I can't be of more help at the moment, but family comes first as I'm sure you understand.
Thanks,
GSLEON3
Aboslutely man. You go take care of your family. I will pray for God to guide you all through this trying time.
On the Kaiser note, I found after further studying of some threads, a solution to my issue where I was stuck in bootloader. I think this will apply to anyone that is stuck in bootloader with the usb/serial showing at the bottom and when they try to flash a new rom is goes to 100%, but the are still stuck on the boot screen.
After reading more threads, it appeared that there was some sort of disconnect between the usb and the phone. Since my PC was stating that it was successfully completing the flash, that shows that it was not getting any type of error from the phone. After reading a thread I simply blew in my tilt usb port and used my stylus to try to straighten it out as one of your post state to ensure the usb connection is straightor it may give mtty an issue.
Once I messed with my USB port, the phone came back to life and everything was fine. Everything was rebooted and all my info was lost however. I was even able to successfully flash a new ROM.
In closing, if anyone is stuck in bootloader mode and their flash goes to 100% and doesn't fix their issue, tell them to clean and straighten their usb connection.
Solution for Those Stuck in Bootloader
Here is the link to the initial thread I started for my issue
http://forum.xda-developers.com/showthread.php?t=406221
I found after further studying of some threads, a solution to my issue where I was stuck in bootloader. I think this will apply to anyone that is stuck in bootloader with the usb/serial showing at the bottom and when they try to flash a new rom is goes to 100%, but the are still stuck on the boot screen.
After reading more threads, it appeared that there was some sort of disconnect between the usb and the phone. Since my PC was stating that it was successfully completing the flash, that shows that it was not getting any type of error from the phone. After reading a thread I simply blew in my tilt usb port and used my stylus to try to straighten it out as one of your post state to ensure the usb connection is straightor it may give mtty an issue.
Once I messed with my USB port, the phone came back to life and everything was fine. Everything was rebooted and all my info was lost however. I was even able to successfully flash a new ROM.
In closing, if anyone is stuck in bootloader mode and their flash goes to 100% and doesn't fix their issue, tell them to clean and straighten their usb connection.

Phone Dead After updating to magic port!!!!

i followed the instructions to the letter and after it was done
i was presented with a picture of an IC microchip and an arrow pointing down.
i restarted the phone and now it wont start.
i cant get into bootloader mode or recovery mode...
Please help me get my phone back!!!!
did you let it finish? the ic microchip and arrow pointing thing? or did you yank out the battery?
i panicked and yanked out the battery...i killed it, didnt i?
I think he didn't let the phone finish and restarted the phone cause it wasa taking too long if that's the case 99.0% the phone is bricked. It happend to somebody else here already. Jy
He just call tmobile and told them the wasn't turning on and they send him a replacement.
I think this is something that needs to be added to the flashing roominstructions.
slyfury said:
i panicked and yanked out the battery...i killed it, didnt i?
Click to expand...
Click to collapse
Im sorry man, you did the one thing you shouldnt have while flashing
Perrosky said:
I think he didn't let the phone finish and restarted the phone cause it wasa taking too long if that's the case 99.0% the phone is bricked. It happend to somebody else here already. Jy
He just call tmobile and told them the wasn't turning on and they send him a replacement.
I think this is something that needs to be added to the flashing roominstructions.
Click to expand...
Click to collapse
i agree 100% please add that to the instruction for noobs like me
oh well, i just hope i get a replacement quickly
that happened to me so i called t-mo and told them that my g1 wont turned on at all and tried the other battery so they send me a replacement. of course i was a noob back then. i learned my lesson in a hard way so i suffer a week without my precious g1 lol.
slyfury said:
i followed the instructions to the letter and after it was done
i was presented with a picture of an IC microchip and an arrow pointing down.
i restarted the phone and now it wont start.
i cant get into bootloader mode or recovery mode...
Please help me get my phone back!!!!
Click to expand...
Click to collapse
also once you called t-mo do not let them know that youre modifying your phone otherwise they will not send you another handset.
slyfury said:
i followed the instructions to the letter and after it was done
i was presented with a picture of an IC microchip and an arrow pointing down.
i restarted the phone and now it wont start.
i cant get into bootloader mode or recovery mode...
Please help me get my phone back!!!!
Click to expand...
Click to collapse
how about take out the sdcard and connect it to the computer, put the jfr33 in it, and flash your phone again. It works
also he could try getting into recovery mode using adb or sumthin...i am not too sure about it...but i think it can be done..!!!
tannyfiles said:
also he could try getting into recovery mode using adb or sumthin...i am not too sure about it...but i think it can be done..!!!
Click to expand...
Click to collapse
If the phone can't reach the bootloader or recovery console I don't think ADB is going to work but I could be wrong.
patience is a virtue
your topic title is misleading and could lead users who haven't tried yet to be too wary about flashing over to Haykuro's builds...
Ultimately...your phone didn't mess up after flashing 4.X..YOU messed up.
if you cant turn on youre g1 then it is dead, even if you connect it to pc or what if it cant be turned be on, it is dead cuz thats what happened to me so just call t-mo and tell them youre phone wont turn on and you tried another battery still wont turn and DO NOT tell them you modify or even saying you attemped to modify your g1's rom.
the best thing for him to do would be flash rc29 nbh and start from scratch...the phone is more than likely not bricked.
korndub said:
the best thing for him to do would be flash rc29 nbh and start from scratch...the phone is more than likely not bricked.
Click to expand...
Click to collapse
To my opinion, i do not think the phone is bricked since there is no hardware issue is involving, it's the software itself, if he can access to the root of the sd card, problem is solved.
but oh well, i would call Tmobile and request a new shinny phone . wait... they will send a refurbished one won't they? oh noo...
I have a similar problem, i was attempting to move apps to the sd card, partitioned it, installed the lucidrem rom and then started using his code and the flashing android loop started, turned it off and back on and still the flashing android, i used the fastboot method to restore my nandroid backup, and the phone is back to working, my problem is that i cant access recovery mode.
everything else is fine, just when i try to load the recovery mode it just stays on the boot screen, can anybody help a newbie out?
the bootloader works, and the phone can load normally, but the recovery mode wont start.
cueballv2 said:
I have a similar problem, i was attempting to move apps to the sd card, partitioned it, installed the lucidrem rom and then started using his code and the flashing android loop started, turned it off and back on and still the flashing android, i used the fastboot method to restore my nandroid backup, and the phone is back to working, my problem is that i cant access recovery mode.
everything else is fine, just when i try to load the recovery mode it just stays on the boot screen, can anybody help a newbie out?
the bootloader works, and the phone can load normally, but the recovery mode wont start.
Click to expand...
Click to collapse
That happened to me also. When I installed lucidrem's rom the recovery would work. What it actually was that when you first rooted your g1 do you rmr installing the recovery img? Well its pretty much the same thing lucidrems rom didn't have a recovery img command line attatched to it. I just installed recovery again from the terminal emulator just like it said in the root your g1 thread.
Atleast that is my side of the story. I don't anything about coding. So I could be wrong but that was just my experience.
bigballa said:
That happened to me also. When I installed lucidrem's rom the recovery would work. What it actually was that when you first rooted your g1 do you rmr installing the recovery img? Well its pretty much the same thing lucidrems rom didn't have a recovery img command line attatched to it. I just installed recovery again from the terminal emulator just like it said in the root your g1 thread.
Atleast that is my side of the story. I don't anything about coding. So I could be wrong but that was just my experience.
Click to expand...
Click to collapse
wow, thanks alot for your help, reflashed the recovery.img and it worked a treat, thought id bricked it good and proper, but your advice worked, thanks again.

Technical Think Tank for Bricked G1's

I started this thread as a constructive and positive place for those of us that have recently lost our G1's or ADP's. I am going to document all my settings, Radio version, Firmware, Build info, etc here and hopefully reverse engineer this issue until I have an answer. If anyone has any hardware engineering information on this device it would be greatly appreciated. I'm even willing to host a private forum from my site to work on this.
Thanks everyone for your continued hard work and Haykuro, you're still the man!
-JFv1.43 RC9 firmware (just did this one update, not the radio update)
-1 GB micro SD which was deliverd with the phone
-Google's Developers Edition
-rooted
-sim ulocked
-almost fully loaded about 80 % battery
-everything went fine, the update went fine, restarting, and then no response and always and always the same android screen,
now im trying to crash it by low battery, not by just take the battery out, maybe this'll work (but I dont think so)
don't know anything else
Partioned Fat32/EXT2 1GB SDcard from t-mobile
Flashed RC29 via Bootloader .NBH file
Rooted with RC29
Updated to RC33
Flashed Hard SPL
Flashed JF v1.5 ADP Lucid MOD - did APPs2SD and Dalvik2SD
Flash 2.22.19.26I Radio
Flashed Grafitti Citrus Theme JFv1.50 Beta
Flashed H Special SPL with battery at 89% - saw it update, rebooted on its own, saw the chip with the arrow on it and it rebooted. once after that it hanged. I waited 5 minutes and then took the battery out. Got my sdcard reader, renamed the jf v1.5 to update to reflash like instructed. powered the phone with home+power and got nothing but a hang on t-mobile G1 screen.
Both phones were done the same. One phone bricked and one phone flashed the SPL.
I wonder if the Dream responds to goldcards like other HTC phones do...
That's how we fixed our Heralds, which is how the Elf's got their fix, etc.
ivanmmj said:
I wonder if the Dream responds to goldcards like other HTC phones do...
That's how we fixed our Heralds, which is how the Elf's got their fix, etc.
Click to expand...
Click to collapse
Goldcard as in a specialized SIM?
d474rpr said:
Goldcard as in a specialized SIM?
Click to expand...
Click to collapse
Goldcards as in a specialized SD card
d474rpr said:
Goldcard as in a specialized SIM?
Click to expand...
Click to collapse
You convert a SD card into a Goldcard and the phone will read it and allow the phone to flash ANY NBH file, regardless of CID, etc etc.
MosquitoD4K said:
-JFv1.43 RC9 firmware (just did this one update, not the radio update)
-1 GB micro SD which was deliverd with the phone
-Google's Developers Edition
-rooted
-sim ulocked
-almost fully loaded about 80 % battery
-everything went fine, the update went fine, restarting, and then no response and always and always the same android screen,
now im trying to crash it by low battery, not by just take the battery out, maybe this'll work (but I dont think so)
don't know anything else
Click to expand...
Click to collapse
This has happened to me many times when I didn't wipe (the PHONE ). Take the battery out, place back in and hold Home + Power to get into menu. Type alt + w to wipe, afterwards, alt + s to apply update.zip from sdcard, then Home+Back to restart. The first time loading, it can take up to ten minutes to get past the Android screen (mine took 7-10 minutes), so be patient.
Post back with any results.
ivanmmj said:
You convert a SD card into a Goldcard and the phone will read it and allow the phone to flash ANY NBH file, regardless of CID, etc etc.
Click to expand...
Click to collapse
that wont work i just read the write up. In order for the goldcard to work, the g1 has to go into fastboot, which none of our devices can go into fastboot nor recovery. I even formatted a sdcard to start the process but when i got to the fastboot i was so disappointed.
One detail, when i flashed the new spl I was doing something else and when i check my phone it back to recovery utility windows itself ,it was in 15 20 minute, after that i reinstalle jf1.5 and all worked ok
what this means. if you are flashing your phone and before these process finishes your take out you battery, you can bricking you phone. take patience and wait.
Good luck
ps:i change the final text for sir*mez
sir*mez said:
that wont work i just read the write up. In order for the goldcard to work, the g1 has to go into fastboot, which none of our devices can go into fastboot nor recovery. I even formatted a sdcard to start the process but when i got to the fastboot i was so disappointed.
Click to expand...
Click to collapse
satru said:
One detail, when i flashed the new spl I was doing something else and when i check my phone it back to recovery utility windows itself ,it was in 15 20 minute, after that i reinstalle jf1.5 and all worked ok
what this means. if you are flashing your phone and before these process finishes your take out you battery, you and only you bricking you phone. take patience and wait.
Good luck
Click to expand...
Click to collapse
this happened to the one that bricked.
Flashed H Special SPL with battery at 89% - saw it update, rebooted on its own, saw the chip with the arrow on it and it rebooted. once after that it hanged. I waited 5 minutes and then took the battery out. Got my sdcard reader, renamed the jf v1.5 to update to reflash like instructed. powered the phone with home+power and got nothing but a hang on t-mobile G1 screen.
Both phones were done the same. One phone bricked and one phone flashed the SPL. So yes I guess I bricked one phone but a miracle happened with the other one. the one that flashed properly went into the recovery on its own right after the boot, but not in no 15-20 min wait like you said. you sure need to stop the blaming. i am not blaming anyone for my bricked phone, im just trying to find a solution. you are going to get this locked because of the bickering.
hey sir*mes was no my intentions blaming to anyone , i only want to say that all need to give more time to flash before take out the battery. only that.
i will do something for you , i will change the text, happy?
Good luck
sir*mez said:
this happened to the one that bricked.
Flashed H Special SPL with battery at 89% - saw it update, rebooted on its own, saw the chip with the arrow on it and it rebooted. once after that it hanged. I waited 5 minutes and then took the battery out. Got my sdcard reader, renamed the jf v1.5 to update to reflash like instructed. powered the phone with home+power and got nothing but a hang on t-mobile G1 screen.
Both phones were done the same. One phone bricked and one phone flashed the SPL. So yes I guess I bricked one phone but a miracle happened with the other one. the one that flashed properly went into the recovery on its own right after the boot, but not in no 15-20 min wait like you said. you sure need to stop the blaming. i am not blaming anyone im just trying to find a solution. you are going to get this locked because of the bickering.
Click to expand...
Click to collapse
sir*mez said:
that wont work i just read the write up. In order for the goldcard to work, the g1 has to go into fastboot, which none of our devices can go into fastboot nor recovery. I even formatted a sdcard to start the process but when i got to the fastboot i was so disappointed.
Click to expand...
Click to collapse
So what harm would it do to try? From what I remember the goldcard on herald was supposed to get us into the bootloader even when we couldn't normally.
Let me be perfectly clear, those of us with the issue of a bricked device from loading the SPL from Haykuro are experiencing an actual case of being bricked.
Read carefully.
The phone WILL NOT turn on!!!!
We are looking for a solution that runs as far back as actually burning the SPL image directly to the phone's memory. I am even willing to try a hardware to hardware method to accomplish this.
I know the phone is still somewhat responsive because my laptop detects the USB connection to the phone but it will not recognize the device.. obviously because the communication is broken since the phone is dead. The power LED will turn on but only after I remove the battery first. Once I press the POWER key the LED turns off and will not light again until I remove and replace the battery.
Solutions that we are trying:
GoldCard method.
Looks like a couple of us have tried this but since fastboot can't see the device then we can't use this method unless someone knows something super seceret.
Crashing the device by allowing the battery to fully discharge. Unlikely but trying anyway.
Any other ideas?????
Thanks everyone for helping thus far!
neoobs said:
So what harm would it do to try? From what I remember the goldcard on herald was supposed to get us into the bootloader even when we couldn't normally.
Click to expand...
Click to collapse
I tried it and so far no luck...
neoobs said:
So what harm would it do to try? From what I remember the goldcard on herald was supposed to get us into the bootloader even when we couldn't normally.
Click to expand...
Click to collapse
ok but the phone wont go into bootloader. which is what im trying to get it to do. if i get it to bootloader i know i can fix it. even if it went to the recovery i could fix it. but I get nothing.
in order to create a goldcard for the dream it has to read the sdcard off fastboot which i cant get into.
d474rpr said:
Let me be perfectly clear, those of us with the issue of a bricked device from loading the SPL from Haykuro are experiencing an actual case of being bricked.
Read carefully.
The phone WILL NOT turn on!!!!
We are looking for a solution that runs as far back as actually burning the SPL image directly to the phone's memory. I am even willing to try a hardware to hardware method to accomplish this.
I know the phone is still somewhat responsive because my laptop detects the USB connection to the phone but it will not recognize the device.. obviously because the communication is broken since the phone is dead. The power LED will turn on but only after I remove the battery first. Once I press the POWER key the LED turns off and will not light again until I remove and replace the battery.
Solutions that we are trying:
GoldCard method.
Looks like a couple of us have tried this but since fastboot can't see the device then we can't use this method unless someone knows something super seceret.
Crashing the device by allowing the battery to fully discharge. Unlikely but trying anyway.
Any other ideas?????
Thanks everyone for helping thus far!
Click to expand...
Click to collapse
Are you saying your screen doesn't turn on?
neoobs said:
Are you saying your screen doesn't turn on?
Click to expand...
Click to collapse
No, I'm saying it doesn't turn on.
d474rpr said:
No, I'm saying it doesn't turn on.
Click to expand...
Click to collapse
The same happens on Heralds when the imgfs is messed up. To fix it, we force it to go into the bootloader mode and it does turn on. I wonder if it's something similar.
I meantioned in the big main topic an idea though I dont think anyone saw it.
In the past for other phones I was able to make recoveries using the computer while it was in the boot loop.
Anyone with the brick, try to see what happens when you do this:
adb remount
After the "T-Mobile G1" screen shows up. See if it says mount sucessful. I would try though it does not stay on the screen too long for me, not only that it might work for me just because it continues fine so its inconclusive.
If you get lucky and it says remount successful, you could try this:
adb shell recovery
I am not sure of the commands to follow from there, but it might allow you to flash a different update.zip file from the command line. If you get lucky like that, look up the commands and see how that might go. There has to be a way to communicate to the hardware when that screen comes up. Its good that that screen comes up, because it means its not 'fried' so to speak, it just has a misconfigured loader which doesnt have the correct set of instructions (good point about the different types of boards, thats most likely the issue) for THAT board. I would go back to the one that worked previously.

[Q] Samsung Galaxy S4 mini I9192 , soft bricked.

Hello , looking for help to unbrick a partially bricked phone that allows me to turn on and use mostly everything , it seems to reboot itself every once in awhile. I can goto Kies and and try to repair but that doesn't work , also have odin with factory file and that shows Fail every time i try that. Hoping someone can help try to get back to factory settings.
Oh and i have read for 2 days here downloaded files and tried everything i can , but nothing seems to work. And when i restart phone it seems to go back to exactly where i left when it got bad root file or something. In the phone part even after i erase calls , it shows the people that called that day every time it gets restarted.
If anyone can help and walk me through , i'd be greatly appreciated. And i've watched i don't know how many youtube vid's on trying to get this back to factory mode.
Thank you.
just go into download mode and flash stock rom through odin.....
mohit378 said:
just go into download mode and flash stock rom through odin.....
Click to expand...
Click to collapse
I've tried mutiple times and always comes up FAILED.
Tried Kies option also....
Apparantly its stuck in Titanium backup mode and occasionally does a reboot on its own sometimes. But even if i try to reboot after erasing tons of stuff out of it.... it comes back to what it was or how it was. So basically the titanium even though it shows up nowhere in my apps or phone... it keeps reverting my phone back to where it was when it got messed up.....
Try this
redskies4you said:
Hello , looking for help to unbrick a partially bricked phone that allows me to turn on and use mostly everything , it seems to reboot itself every once in awhile. I can goto Kies and and try to repair but that doesn't work , also have odin with factory file and that shows Fail every time i try that. Hoping someone can help try to get back to factory settings.
Oh and i have read for 2 days here downloaded files and tried everything i can , but nothing seems to work. And when i restart phone it seems to go back to exactly where i left when it got bad root file or something. In the phone part even after i erase calls , it shows the people that called that day every time it gets restarted.
If anyone can help and walk me through , i'd be greatly appreciated. And i've watched i don't know how many youtube vid's on trying to get this back to factory mode.
Thank you.
Click to expand...
Click to collapse
I don't know if the fail you get in Odin may be caused by having the wrong settings. I have ran into a few tutorials online that use odin, each one had a specific way. Try running it again with all the options unchecked except for the Auto Reboot. Also make sure you place the correct file(s) in the correct slot. example: any bootloader file goes into the bootloader slot, etc. make sure its checked. Then run again, this may be the only reason your getting a fail, it may have nothing to do with Odin or your phone.
Of course disregard this message if you had already fixed you problem. Also another possible fix would be to use ADB command to push the files to your phone, I suggest looking into it, there is a good amount of info on it online. It could help down the line with future issues to know ADB. Here is a website I found helpful, it is a guide to using ADB sideload to save bricked devices. ------- (android-revolution-
hd.blogspot.com/2013/12/ow-to-use-adb-sideload.html) note: just copy everything after the dashes and in between the parenthesis and paste into url bar on browser. sorry i have to be difficult, first time posting on this site and they wont let me post in a link, but this guide may be the answer to all your phone trouble. Plus I know how you feel, I just bricked my phone too and I know how agravating it is when nothing works.
Good luck and let me know how it goes
Thanks
BAMTek.Inc said:
I don't know if the fail you get in Odin may be caused by having the wrong settings. I have ran into a few tutorials online that use odin, each one had a specific way. Try running it again with all the options unchecked except for the Auto Reboot. Also make sure you place the correct file(s) in the correct slot. example: any bootloader file goes into the bootloader slot, etc. make sure its checked. Then run again, this may be the only reason your getting a fail, it may have nothing to do with Odin or your phone.
Of course disregard this message if you had already fixed you problem. Also another possible fix would be to use ADB command to push the files to your phone, I suggest looking into it, there is a good amount of info on it online. It could help down the line with future issues to know ADB. Here is a website I found helpful, it is a guide to using ADB sideload to save bricked devices. ------- (android-revolution-
hd.blogspot.com/2013/12/ow-to-use-adb-sideload.html) note: just copy everything after the dashes and in between the parenthesis and paste into url bar on browser. sorry i have to be difficult, first time posting on this site and they wont let me post in a link, but this guide may be the answer to all your phone trouble. Plus I know how you feel, I just bricked my phone too and I know how agravating it is when nothing works.
Good luck and let me know how it goes
Click to expand...
Click to collapse
Thanks Bam.... I'm just in need of all stock files Including the PIT file which is like impossible to find it seems to try and get this phone back to factory reset mode..... The phone actually works but anytime it reboots or save anything...ect.... it just reverts back to when it got tripped up. Thanks again for anyone's help.

[Completed] Recovery mode is gone, Factory mode is gone, help me XDA you're my only hope...

So here is a string of steps I've already been through in trying to save my bricked Nexus 6: [Can't post outside link yet...]
Basically I got the 'your phone is corrupt' message from google and it kept forcibly shutting down. It would not boot up so someone suggested I side load a rescue OTA. At this point recovery existed and I went through all the steps and had it installing, only to fail mid-way through (~52%) and give me a 'read error' on my command prompt. I started the whole process over again just fine and it got to 73% before 'read error' failing again. I thought no big deal, I'll just keep doing this until it gets to 100%. Nope, recovery is gone. I cannot get there anymore. I start into Fastboot mode and scroll to recovery and hit power and it just goes to a new Fastboot screen and keeps flashing every time I try to select it. The Bootloader logs give me a 'failed to validate boot image: ret=-1' message and says 'Boot up failed.'
I can't find a single guide online that doesn't require recovery mode to work. At this point I don't care about my data and just want to get this phone working again before I throw in the towel and pay Motorola $175 for a refurb. I'm just barely over a year too. The Nexus 'expert' gave up and blamed the memory and maybe he is right but I wanted to run this by you guys first. This phone was completely stock and unrooted.
The only reason why I feel there is still a chance is because when I connect USB my computer reads it as an Android Device in Device Manager with 'Android Bootloader Interface' as a sub device. If the computer can read it, isn't there a chance that some kind of software exists that can forcibly load a new bootloader onto this phone without recovery? I'm 'competent' with computers and android phones but I haven't rooted or done any custom stuff in years so I'm at a loss for what's out there.
Thanks in advance for any help you can give me, even if it's to tell me I'm SOL.
Ok so far I have tried to load a custom recovery but that requires an unlocked bootloader. Then I tried using a toolkit to flash stock as a soft-bricked device but that also requires an unlocked bootloader and I can't unlock the damn bootloader. You know, I thought I was just playing it safe by leaving this phone as-is instead of playing around with it but it looks like I screwed myself by doing so.
Is this the wrong forum for this question?
JQ3 said:
Is this the wrong forum for this question?
Click to expand...
Click to collapse
Sorry for the delay
We have a dedicated help section for your device here
http://forum.xda-developers.com/nexus-6/help
Ask there to receive help
Good luck

Categories

Resources