Database Info

[Q] Nexus S 4G won't boot past Google Screen!!

I tried rooting my phone, but when I flashed CWM my Nexus S stopped booting... it freezes on the Google screen in the intro. I can boot into Fastboot, and cwm, but I cant connect the Internal memory to the computer without it booting like it is supposed to. Does anybody know of anything I can do to fix my phone and bring it back to stock??

There are guides for returning to stock stickied in the Nexus S 4G Android Development forum.
Before you do that though, try flashing a different recovery, like the one linked to here or here.
Btw, which guide did you use? You're not the first person to have this problem, and it's really bugging me (though probably not as much as it's bugging you :-o).

Maximilian Mary: I tried to post the link, but since I'm a new member I have to wait 8 posts before I can post a URL.... :/
I will try a different recovery, but how would I flash a rom if I can connect my phone via usb mount?

deadzunehd said:
Maximilian Mary: I tried to post the link, but since I'm a new member I have to wait 8 posts before I can post a URL.... :/
Click to expand...
Click to collapse
What's the title of the thread?
.
I will try a different recovery, but how would I flash a rom if I can connect my phone via usb mount?
Click to expand...
Click to collapse
I'm a little out of my depth here, but I think it's
fastboot flash system system.img.
You don't need to put the rom image on the sdcard. Just put it in the same folder as fastboot.

It was titled "How to Root Nexus S!"
And I will try to flash recovery and try that rom command, thank you )

deadzunehd said:
It was titled "How to Root Nexus S!"
And I will try to flash recovery and try that rom command, thank you )
Click to expand...
Click to collapse
Hmmm. I can't find that exact title. Could you pm me the link?

deadzunehd said:
thank you )
Click to expand...
Click to collapse
There's a button for that.

I got the link. Thanks. I looks like you flashed a boot image that is incompatible with your phone. That guide was for the T-Mobile Nexus S. (Why they're screwing with the boot.img to begin with, I really don't understand.)
Download the attached file, and unzip it to the same folder as fastboot. The md5 sum is d4a9508f9321eb25df3383f00f571e8b. Then
Code:
fastboot flash boot boot.img
You'll probably also want to use one of the recoveries listed above to
Code:
fastboot flash recovery recovery.img
, but leave system alone for now. Flash that only as a last resort.

deadzunehd said:
I tried rooting my phone, but when I flashed CWM my Nexus S stopped booting... it freezes on the Google screen in the intro. I can boot into Fastboot, and cwm, but I cant connect the Internal memory to the computer without it booting like it is supposed to. Does anybody know of anything I can do to fix my phone and bring it back to stock??
Click to expand...
Click to collapse
I had this problem after flashing the wrong ROM onto my phone. I got the phone back to stock using ODIN.
My thread can be found here
http://forum.xda-developers.com/showthread.php?p=14172335#post14172335
hope it helps

Acnescar said:
I had this problem after flashing the wrong ROM onto my phone. I got the phone back to stock using ODIN.
My thread can be found here
http://forum.xda-developers.com/showthread.php?p=14172335#post14172335
hope it helps
Click to expand...
Click to collapse
OMG!! im having the same issue. could you please post the link for ODIN so i can return to stock and take it from there please? I rely on my phone so much and i need it asap thank you.

same problem with me.
but in my case, the phone not only freeze after the google logo before boot. I tried several times to pull the battery and start the phone again, it took several times until the phone can boot normally again.
After that, my nexus s can work as usual. but it only takes 3-4 hour until it freeze/hangs or reboot automatically and show image of green robot lay down with red alert triangle...
sometimes I noticed all application force closed like gmail, gtalk, etc. (its a basic apps instead of 3rd party app)
History :
- root GB 2.37 using superoneclick
- upgrade OTA to ICS 4.04
- problem happens
- root using guide : nexusshacks.com
- unroot using guide : nexusshacks.com
- back to factory setting on GB 2.34
- upgrade OTA to ICS 4.04
- Still got that problem.....
I'm using Nexus S 4G Sprint, pls help me guys...

nexus s won't boot
I had the same problem and read elsewhere that heating the phone with a hairdryer solves the problem.
I must say, indeed it did.
I removed the battery and the SIM card, then heated up the phone (so it really feels warm) put back the battery and sim and simsalebim the phone started again. and is still working since (now already a few day's)
It seems that a component in the phone is heat sensitive, the question in my mind is when will this show again and do I need to consider buying a new phone.
But sofar it works
PS I also tried hard reset factory reset the lot, but in the end only heating up helped.
Good luck, David

I fixed this problem! but I had to wipe all user data by rooting it using nexusrootICS. It finally boots up and the phone works now... that's all I need.

[Q] About CM7

I have Kyrillos Mod 7.0 now.. non oc.. If i flash CM7 with it preinstalled (not talkin about dual boot) will CM7 replace it?

Yes it will
Flashing means replacing files in the nand chip in the phone i.e. Replacing the current rom

cdesai said:
Yes it will
Flashing means replacing files in the nand chip in the phone i.e. Replacing the current rom
Click to expand...
Click to collapse
After replacing, its the only ROM there ri8? And I can install it on Kyrillos' ri8?

Alex664 said:
After replacing, its the only ROM there ri8? And I can install it on Kyrillos' ri8?
Click to expand...
Click to collapse
yeah, if u dont use dual boot, its only rom, then. Yes, u can install it over Kyrillos'.

tadeas482 said:
yeah, if u dont use dual boot, its only rom, then. Yes, u can install it over Kyrillos'.
Click to expand...
Click to collapse
Thanks and thanked you

cdesai said:
Yes it will
Flashing means replacing files in the nand chip in the phone i.e. Replacing the current rom
Click to expand...
Click to collapse
Going a bit off-topic, but cant help it.
cdesai- i guess you can replace Chuck Norris with our own Rajnikanth.

Sos! Help asap! What do i do now?
I have a problem. First off, I'm a newb to android stuff and don't know a whole lot(especially technical terms like bootloader, flashing, etc.). But after researching online and reading some forums, i really want to update my phone to gingerbread because the HK froyo version can't get flash or most froyo apps.
When i heard the CM GB ROM, i downloaded odin and flashed it. Afterwards, the rom manager clockworld page popup and i rebooted the phone off course. Now everytime i boot up my phone, it gets stuck on the CM7 logo page and keeps loading and reloading for 30 sec. and continue to popup and do the whole sequence again. HELP PLEASE! THIS IS MY ONLY PHONE AND MY MOM IS GONNA KILL ME IF SHE FIND OUT! If theres a way, please tell me.
P.S- I am very stupid so please explain in simple way but elaborate details. I appreciate all the help i can get

mcmikechan123 said:
I have a problem. First off, I'm a newb to android stuff and don't know a whole lot(especially technical terms like bootloader, flashing, etc.). But after researching online and reading some forums, i really want to update my phone to gingerbread because the HK froyo version can't get flash or most froyo apps.
When i heard the CM GB ROM, i downloaded odin and flashed it. Afterwards, the rom manager clockworld page popup and i rebooted the phone off course. Now everytime i boot up my phone, it gets stuck on the CM7 logo page and keeps loading and reloading for 30 sec. and continue to popup and do the whole sequence again. HELP PLEASE! THIS IS MY ONLY PHONE AND MY MOM IS GONNA KILL ME IF SHE FIND OUT! If theres a way, please tell me.
P.S- I am very stupid so please explain in simple way but elaborate details. I appreciate all the help i can get
Click to expand...
Click to collapse
Try to flash some stable FROYO Rom first. Kryillos ROM 8.2.1 is very Good ROM to flash. And you will get the same feel of gingerbread in it unless ofcourse you want to see 2.3.4/2.3.5 on your phone try flashing CM7alpha 6 allover again. Hope this helps.
Hit Thanks if i helped you in anyway.

mcmikechan123 said:
I have a problem. First off, I'm a newb to android stuff and don't know a whole lot(especially technical terms like bootloader, flashing, etc.). But after researching online and reading some forums, i really want to update my phone to gingerbread because the HK froyo version can't get flash or most froyo apps.
When i heard the CM GB ROM, i downloaded odin and flashed it. Afterwards, the rom manager clockworld page popup and i rebooted the phone off course. Now everytime i boot up my phone, it gets stuck on the CM7 logo page and keeps loading and reloading for 30 sec. and continue to popup and do the whole sequence again. HELP PLEASE! THIS IS MY ONLY PHONE AND MY MOM IS GONNA KILL ME IF SHE FIND OUT! If theres a way, please tell me.
P.S- I am very stupid so please explain in simple way but elaborate details. I appreciate all the help i can get
Click to expand...
Click to collapse
Did u wipe data/factory reset at the cwm recovery?
Sent from my GT-I5801 using XDA App

HELP! Brick Bug!

So long story short, my tab was running stock ICS (rooted, with temp CWM/cwm.zip). I decided to try a new rom (paranoid android) so I backed up everything via CWM and I flashed the new rom. But I forgot to do a factory reset before doing so which resulted in a bootloop. I returned to CWM to try to restore the previous ROM, all seemed to be fine and the tab restarted but was also bootlooped. Now I can't even access the stock recovery to acess CWM, I get an error message:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC code : THL
Successfully applied multi-CSC
E :failed to mount / system (invalid argument) <in red.
Is there anything I can do to return to my stock ROM?!
Do I have the Brick Bug?

rumpypumpy said:
So long story short, my tab was running stock ICS (rooted, with temp CWM). I decided to try a new rom (paranoid android) so I backed up everything via CWM and I flashed the new rom. But I forgot to do a factory reset before doing so which resulted in a bootloop. I returned to CWM to try to restore the previous ROM, all seemed to be fine and the tab restarted but was also bootlooped. Now I can't even access the stock recovery to acess CWM, I get an error message:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC code : THL
Successfully applied multi-CSC
E :failed to mount / system (invalid argument) <in red.
Is there anything I can do to return to my stock ROM?!
Click to expand...
Click to collapse
Can it get into download mode? If so try flash a stock rom with odin. Im not a sgt user but i am a samsung phone user and usualy when i forget to wipe all i have to do is go back into recovery. Then wipe everything and flash the same rom. NEVER go straight to a backup unless you pass setup. Then it can create a link almost so it supports going back. Or so thats what ive been told by devs on other forums...sounds kinda wierd tho but anyway if you forget to do something while flashing roms then go back indo recovery and do it again
Sent from the phone of Gamers

gmaster1 said:
Can it get into download mode? If so try flash a stock rom with odin. Im not a sgt user but i am a samsung phone user and usualy when i forget to wipe all i have to do is go back into recovery. Then wipe everything and flash the same rom. NEVER go straight to a backup unless you pass setup. Then it can create a link almost so it supports going back. Or so thats what ive been told by devs on other forums...sounds kinda wierd tho but anyway if you forget to do something while flashing roms then go back indo recovery and do it again
Sent from the phone of Gamers
Click to expand...
Click to collapse
It loads the amination for the stock recovery, then I get the error message I posted above. I need to get onto the stock recovery to get into CWM. Im not too sure what to do at the moment...

rumpypumpy said:
It loads the amination for the stock recovery, then I get the error message I posted above. I need to get onto the stock recovery to get into CWM. Im not too sure what to do at the moment...
Click to expand...
Click to collapse
Thats a messege saying the system has broke basicly because you went straight to a backup. Download mode and odin are your only hope
Sent from the phone of Gamers

gmaster1 said:
Thats a messege saying the system has broke basicly because you went straight to a backup. Download mode and odin are your only hope
Sent from the phone of Gamers
Click to expand...
Click to collapse
I forgot about download mode. I'll have a go then I'll report back.
Thanks

Now I'm stuck at the "<ID:0/005> factoryfs.img" stage!
I'm a bit scared of unplugging the tab, what would be the best thing to do now?
EDIT: If I flash a kernel or CWM, would this solve my problem?
Thanks in advance
EDIT:I managed to get CWM working, a step in the right direction

rumpypumpy said:
Now I'm stuck at the "<ID:0/005> factoryfs.img" stage!
I'm a bit scared of unplugging the tab, what would be the best thing to do now?
EDIT: If I flash a kernel or CWM, would this solve my problem?
Thanks in advance
EDIT:I managed to get CWM working, a step in the right direction
Click to expand...
Click to collapse
From CWM wipe data, cache & dalvik & reboot.
And flash this ICS zip file from CWM. if yours is 6800.
http://forum.xda-developers.com/showthread.php?t=1796866

rumpypumpy said:
Now I'm stuck at the "<ID:0/005> factoryfs.img" stage!
I'm a bit scared of unplugging the tab, what would be the best thing to do now?
EDIT: If I flash a kernel or CWM, would this solve my problem?
Thanks in advance
EDIT:I managed to get CWM working, a step in the right direction
Click to expand...
Click to collapse
If cwm works then we both know theres hope
Sent from the phone of Gamers

lsherif said:
From CWM wipe data, cache & dalvik & reboot.
And flash this ICS zip file from CWM. if yours is 6800.
http://forum.xda-developers.com/showthread.php?t=1796866
Click to expand...
Click to collapse
I did everything you said, but the progress bar has been stuck at 75% for over an hour, this has happened with all the ROMs I've tried to install. Is there anything else I could do? I red somewhere that a low battery doesn't allow ROMs to be installed properly.
Although I have no idea of my battery life, I'm just gonna leave it to charge for a bit. I hope everything turns out fine eventually

rumpypumpy said:
I did everything you said, but the progress bar has been stuck at 75% for over an hour, this has happened with all the ROMs I've tried to install. Is there anything else I could do? I red somewhere that a low battery doesn't allow ROMs to be installed properly.
Although I have no idea of my battery life, I'm just gonna leave it to charge for a bit. I hope everything turns out fine eventually
Click to expand...
Click to collapse
Battery life has nothing to do with it. People just say make sure you have high battery incase something happens. I think that it might be a very expensive brick now. Unless anyone else knows then i habe no idea
Sent from the phone of Gamers

gmaster1 said:
Battery life has nothing to do with it. People just say make sure you have high battery incase something happens. I think that it might be a very expensive brick now. Unless anyone else knows then i habe no idea
Sent from the phone of Gamers
Click to expand...
Click to collapse
:crying:
I was reading the following articles:
http://www.xda-developers.com/android/samsung-diligently-working-towards-hardbrick-fix/
http://forum.xda-developers.com/showthread.php?t=1810954
Could this Brick Bug be the source of my problems?
I was running a leaked version of ICS AND I have been using the cwm.zip so there is the possibility

Being unable to flash through either Odin or CWM surely sounds a lot like the brickbug.
If I were you, I'd reboot to download mode, and install a full ROM with repartition + PIT file. If it works, install locerra's CWM (it's one of the few recoveries for our tablet that's confirmed to be brickbug-free), and work as usual. But remember to wipe everything before installing anything through CWM...
If Odin doesn't work, you probably have been hit by the brickbug. However, all is not lost: this guy seems to have found a "fix" for many devices. It involves giving up on all your data and making your onboard storage a couple of GB smaller than it used to be, but it can make your device work again. Read the thread, try to understand it, and (if you can't find another way out) use the PIT file for the GT-6800 provided. If your tab isn't the international WiFi+3G GT-P6800, you may have to ask the guy (hg42) for a PIT tailored to your device.
The other option, in the case of a eMMC-related brick, is to remove all traces of CWM, go to a Samsung store and repair it under warranty, saying "its broke down when I were running that backie upppe thing in kies".

The other option is the better one, as i bricked my note. When i am able to revive it, i am left with 8GB space and it seems real laggy. Change a new motherboard would be better if still cover undr warrantly.
Sent from my GT-P6800 using xda premium

Thanks for the replies guy.
I have decided I will return it as faulty, in the hope it is repaired. I haven't been able to boot into CWM anymore, only the download mode, so I am guessing it is fine to return it as it is?
Thanks

rumpypumpy said:
Thanks for the replies guy.
I have decided I will return it as faulty, in the hope it is repaired. I haven't been able to boot into CWM anymore, only the download mode, so I am guessing it is fine to return it as it is?
Thanks
Click to expand...
Click to collapse
If I were you, I'd return it to something as close to stock as possible.
One suggestion: grab the latest Odin-flashable ROM for your country. You'll get a .tar.md5 file, such as P6800UBLA2_P6800ZTOLA2_ZTO.tar.md5. Try to flash it through Odin, just to see if it works; if it doesn't, write down the name of the .img file that gave you problems. If it works, congratulations, you have your tablet back, and you can stop reading.
Now, Rename that file to .tar (or, remove the .md5 extension), and open it in WinRAR/7zip/whatever. You'll see a lot of .img files inside, including the one that gave you problems. Remove it, and try to flash this new .tar file. If the flash works, proceed to the next paragraph. If it doesn't, write down the name of the .img file that gave you problems, and repeat this paragraph using your new .tar file.
After a flash that works, your device should be as close to stock as possible. Maybe it will even boot, but I wouldn't count on it (try anyway). I'd send it to the repair centre only when it is at this stage.

Steve_max said:
If I were you, I'd return it to something as close to stock as possible.
One suggestion: grab the latest Odin-flashable ROM for your country. You'll get a .tar.md5 file, such as P6800UBLA2_P6800ZTOLA2_ZTO.tar.md5. Try to flash it through Odin, just to see if it works; if it doesn't, write down the name of the .img file that gave you problems. If it works, congratulations, you have your tablet back, and you can stop reading.
Now, Rename that file to .tar (or, remove the .md5 extension), and open it in WinRAR/7zip/whatever. You'll see a lot of .img files inside, including the one that gave you problems. Remove it, and try to flash this new .tar file. If the flash works, proceed to the next paragraph. If it doesn't, write down the name of the .img file that gave you problems, and repeat this paragraph using your new .tar file.
After a flash that works, your device should be as close to stock as possible. Maybe it will even boot, but I wouldn't count on it (try anyway). I'd send it to the repair centre only when it is at this stage.
Click to expand...
Click to collapse
The tab gets stuck at 'factoryfs.img'. I'm a bit cautious since it is the biggest file in the .tar. Isn't the tab 'stock' stock enough as it is?:silly:

rumpypumpy said:
The tab gets stuck at 'factoryfs.img'. I'm a bit cautious since it is the biggest file in the .tar. Isn't the tab 'stock' stock enough as it is?:silly:
Click to expand...
Click to collapse
Thats...a...problem...if it takes longer then 15 mins its bricked...i have been a gt user and devs on other sites told me it was bricked. Maybe there is a solution but...i havnt found one. It should never take too long on one thing in odin.
Sent from the phone of Gamers

rumpypumpy said:
The tab gets stuck at 'factoryfs.img'. I'm a bit cautious since it is the biggest file in the .tar. Isn't the tab 'stock' stock enough as it is?:silly:
Click to expand...
Click to collapse
Even so, flash the other .imgs. You want to be closest to stock, including the recovery (imagine the guys at the Samsung centre manage to enter recovery, just to see CWM: your warranty is now gone). Having all partitions on stock, or at least most of them, can only help your case.

Steve_max said:
Even so, flash the other .imgs. You want to be closest to stock, including the recovery (imagine the guys at the Samsung centre manage to enter recovery, just to see CWM: your warranty is now gone). Having all partitions on stock, or at least most of them, can only help your case.
Click to expand...
Click to collapse
The warrenty is not void unless they find proof of tampering with system files. So basicly yeah...everything that guy said. Get it as close to stock as possible and send.
Sent from the phone of Gamers

Right OK, I definately don't want my warrenty void!
So would it be ok if I flashed 'P6800OXALQ1_P6800XXLQ1_HOME.tar.md5' (minus the factoryfs.img) to my tab?
Thanks

[Q] TF101 unable to boot - unrecoverable bootloader 0x000000004 error

Hi, hope somebody can help me with my B70 TF101, rooted but everything else stock.
Earlier this week I received an Encryption Unsuccesfull message, tablet worked fine in the morning, would not work in the afternoon.
I tried a factory reset (volume down & power, but no luck, it starts but then displays the android with red exclamation mark.
After searching the forum I tried to use Easyflasher's unbricking/ flashing stock firmware tool with the latest Asus update for the US, chose SBK2 as it is a B70, Easyflasher showed succes, however when I tried to reboot the TF I receive the unrecoverable bootloader 0x000000004 error .
Anybody have any ideas what went wrong and how to correct this?
Thank you.

AmstelD said:
Hi, hope somebody can help me with my B70 TF101, rooted but everything else stock.
Earlier this week I received an Encryption Unsuccesfull message, tablet worked fine in the morning, would not work in the afternoon.
I tried a factory reset (volume down & power, but no luck, it starts but then displays the android with red exclamation mark.
After searching the forum I tried to use Easyflasher's unbricking/ flashing stock firmware tool with the latest Asus update for the US, chose SBK2 as it is a B70, Easyflasher showed succes, however when I tried to reboot the TF I receive the unrecoverable bootloader 0x000000004 error .
Anybody have any ideas what went wrong and how to correct this?
Thank you.
Click to expand...
Click to collapse
Can you boot in recovery?
Edit: Err.. did you flash the right ROM? Every one that has that problem is on the Prime, not the TF101. See this thread, brick 1b and 2.

No recovery, I can only get into APX.
Used US_epad-user-9.2.1.27 with Easyflasher. Downloaded from the Asus site.
Lethe6 said:
Can you boot in recovery?
Edit: Err.. did you flash the right ROM? Every one that has that problem is on the Prime, not the TF101. See this thread, brick 1b and 2.
Click to expand...
Click to collapse

AmstelD said:
No recovery, I can only get into APX.
Used US_epad-user-9.2.1.27 with Easyflasher. Downloaded from the Asus site.
Click to expand...
Click to collapse
Any other ideas or suggestions?
Is my TF101 now permanently bricked?

Can you flash it again with easy flasher?

Lethe6 said:
Can you flash it again with easy flasher?
Click to expand...
Click to collapse
I tried reflashing with Easyflasher, it shows success, but gives the same error at reboot.

Can you try an older revision of the firmware?

AmstelD said:
I tried reflashing with Easyflasher, it shows success, but gives the same error at reboot.
Click to expand...
Click to collapse
If flashing stock fails again then try following step
Instead of flashing stock rom, Try flashing recovery(TWRP) through easy flash, if that's a success then get into recovery n DELETE/FORMAT internal memory, cache, dalvik and everything under wipe option... down a custom ROM and flash it.. that might work
Sent from my Transformer using xda app-developers app

Lethe6 said:
Can you try an older revision of the firmware?
Click to expand...
Click to collapse
Looking for an older version of the stock to download, no longer on the Asus site. Where else can I find that? Need a US version of the stock.

udupa82 said:
If flashing stock fails again then try following step
Instead of flashing stock rom, Try flashing recovery(TWRP) through easy flash, if that's a success then get into recovery n DELETE/FORMAT internal memory, cache, dalvik and everything under wipe option... down a custom ROM and flash it.. that might work
Sent from my Transformer using xda app-developers app
Click to expand...
Click to collapse
I have tried to flash TWRP, receive success confirmation, but can not boot into recovery, still giving the unrecoverable boot error message.
Any other suggestions?

Looks like you're using an unsigned loader or something... but at this point I'm not sure how to solve this. Maybe try posting in the easy flasher thread, the author might have some ideas. If you want to start learning the more hardcore stuff, you can take a look here, though it's for a different model but can point you in the right direction.
This guy had the motherboard replaced to fix it.
People having the same problem, you should keep an eye out there as well.
Finally, last ditch effort... maybe roll back to 3.0? See the update in this post.
Even though some help/answers are for different models, they can help you think of new solutions or provide generic tools; it's worth looking into.

Thanks for the assistance. I gave up on the tf101 and bought a Note 2.
Lethe6 said:
Looks like you're using an unsigned loader or something... but at this point I'm not sure how to solve this. Maybe try posting in the easy flasher thread, the author might have some ideas. If you want to start learning the more hardcore stuff, you can take a look here, though it's for a different model but can point you in the right direction.
This guy had the motherboard replaced to fix it.
People having the same problem, you should keep an eye out there as well.
Finally, last ditch effort... maybe roll back to 3.0? See the update in this post.
Even though some help/answers are for different models, they can help you think of new solutions or provide generic tools; it's worth looking into.
Click to expand...
Click to collapse

[Q] HELP! Verizon Galaxy S 5 Bricked / Stuck In Boot Loop

Problem resolved thanks to bweN diorD!

Dark System said:
Hey everyone, I figured this was the right section to post a question, sorry if I was mistaken.
So I recently rooted my phone and tried to install a custom ROM on it, turns out the ROM I selected was probably for the wrong model or something because my screen was just black. So I booted into recovery to try and restore it on the ROM I backed up and it was gone so now I'm kinda ****ed on a phone for now, before I look into buying a new one I wanna see if there's any way I can resolve this and unbrick it.
When I turn the phone on it just loops the booting screen and when I boot into recovery it just has the droid dude with an exclamation mark on it then turns off and does the boot loop.
I was wondering if maybe there's a file I can put on an external drive and it will automatically restore back to stock like on other devices.
I've done a lot stuff like this to my PS3 just never tried it for my phone so I'm just hoping there's a method out there for me, please provide any feedback or questions about it, I'm just trying to get this resolved and I have no time really to research it because of work and a newborn baby plus you guys would know more about it than me so yeah. Thanks!
Click to expand...
Click to collapse
usually when you flash the wrong software to a phone it is toast, but you may be in luck as it still turns on.
video here.
further instruction here.
if that doesnt work... well its not good unfortunately.

Dark System said:
Hey everyone, I figured this was the right section to post a question, sorry if I was mistaken.
So I recently rooted my phone and tried to install a custom ROM on it, turns out the ROM I selected was probably for the wrong model or something because my screen was just black. So I booted into recovery to try and restore it on the ROM I backed up and it was gone so now I'm kinda ****ed on a phone for now, before I look into buying a new one I wanna see if there's any way I can resolve this and unbrick it.
When I turn the phone on it just loops the booting screen and when I boot into recovery it just has the droid dude with an exclamation mark on it then turns off and does the boot loop.
I was wondering if maybe there's a file I can put on an external drive and it will automatically restore back to stock like on other devices.
I've done a lot stuff like this to my PS3 just never tried it for my phone so I'm just hoping there's a method out
for me, please provide any feedback or questions about it, I'm just trying to get this resolved and I have no time really to research it because of work and a newborn baby plus you guys would know more about it than me so yeah. Thanks!
Click to expand...
Click to collapse
Boot into bootloader and flash stock rom using odin..

bweN diorD said:
solution
Click to expand...
Click to collapse
Alright thank you! I'm pretty confident this will work, once the stock ROM file finishes downloading, which it doesn't seem that it wants to work. I've downloaded it 5 times now and every time it's done it's a fail.. I'll keep trying though.

bweN diorD said:
if that doesnt work... well its not good unfortunately.
Click to expand...
Click to collapse
yeah it didn't work, did everything right but when it tries to reboot I get the dead little droid guy.