[Q] G1 stuck at "G1 T-Mobile" Startup screen. How to fix? - G1 Q&A, Help & Troubleshooting

Hello,
Tryed to find similar threads, but found none with the correct answer.
When i tryed to unroot/unflash my phone back to stock something went wrong.
Now when i try to turn my phone on i can only see this "G1 t-Mobile" loadingscreen and nothing else happens.
Ive tryed booting with Home+Power, with Camera+Power and a normal booth, nothing works. Replaced the SD-card with an other one (1GB), first formatted FAT32style, didnt work. Afterwards i put the DREAIMG.nbh file on it and tryed it, but still didnt work. Im all out of options.
Can someone please help?

hoipupe said:
Hello,
Tryed to find similar threads, but found none with the correct answer.
When i tryed to unroot/unflash my phone back to stock something went wrong.
Now when i try to turn my phone on i can only see this "G1 t-Mobile" loadingscreen and nothing else happens.
Ive tryed booting with Home+Power, with Camera+Power and a normal booth, nothing works. Replaced the SD-card with an other one (1GB), first formatted FAT32style, didnt work. Afterwards i put the DREAIMG.nbh file on it and tryed it, but still didnt work. Im all out of options.
Can someone please help?
Click to expand...
Click to collapse
I'm afraid you have a hard bricked phone. Only way out is to jtag it.
http://forum.xda-developers.com/showthread.php?t=591048

i have the same problem in my g1 mobile he is dead now please help me

Did you try going to the Root screen? If you can't go to the root screen, then it might be Bricked, I'm not sure though.
Sent from my T-Mobile G1 using XDA App

I have tryed every button combination possible, and none of them worked
So there is no other way to fix this unless i need to adjust the hardware?

hoipupe said:
I have tryed every button combination possible, and none of them worked
So there is no other way to fix this unless i need to adjust the hardware?
Click to expand...
Click to collapse
I'll simply refer you back to post number 2.

shadowch31 said:
I'll simply refer you back to post number 2.
Click to expand...
Click to collapse
Yes, and thank you for that.
Though, im afraid i'm not competent enough to "JTAG" it as i dont understand 50% of the stuff being said in that post
Also i read you need some equipment like a JTAG Adapter, which i dont have..

hoipupe said:
Yes, and thank you for that.
Though, im afraid i'm not competent enough to "JTAG" it as i dont understand 50% of the stuff being said in that post
Also i read you need some equipment like a JTAG Adapter, which i dont have..
Click to expand...
Click to collapse
Your best bet would be to see if anyone in your area/country who can do it for you probably at a lot cheaper cost than buying a new phone.

Related

Major Problem...

My system locked whilst flashing the CE rom.....
now i have a completely dead pda.. how do i recover from this?
:shock:
nobody ? any ideas at all? or is my xda going back under warranty?
help!!
reboot
If you reboot your pc, and leave the BA in the cradle, and then just execute the updater (romflasher) again, it works fine!
the BA just sits there.. no lights.. no nothing.
if you remove and reseat in the cradel you get the briefest flash of red on the right hand light. then nothing. screen is blank. hard or soft reset do nothing?
pc just says it cannot find pda when you try to update?
i assume its screwed then.
not nessaserily, try to get into bootloader mode....... i think its power button, camera button and soft reset button, tho someone please correct me if im wrong, if you can get into bootloader, then your device is ok, i aint sure how to get out of bootloader after this, but this happened to me when i tried to install windows mobile 2005 on my BA, lol, before i knew it didnt work, obviously, lol, if you open up active sync, click on file and connection settings, untick, allow usb connection, and try to do the upgrade again, but first after you untick that box, and clicked ok, you need to do a hard reset then put it in the cradle. then after you try and upgrade again, this worked for me, try this and let us know if you still cannot do it.... 8)
I've flashed my XDA, XDAII and MDAIII many times. Ocassionally, something has gone wrong, but I've always been able to recover the situation. But I've just tried to reflashed 1.40 and the PC crashed at 55% and now I'm in the same boat as you. I've tried all the tricks and it is completely dead. Fortunately a new one arrives in the morning.
I think you'll also have to swap your phone. If it won't go into bootloader, it's dead.
thing is, i think the warranty is void if you play around with upgrading and screw up,
im always happy to help someone fix it, as i done it many times with my own, and fixed other pda's too...... 8)
wont go into bootloader mode..
8-(
U shdn't have removed it from cradle.....See if u get a sound in yr PC when u place your device in the cradle.If yes rthen it is detected...
ffelan said:
wont go into bootloader mode..
8-(
Click to expand...
Click to collapse
FFelan,
Last ditch, pull the battery off, and allow the backup battery to fully drain. (60+ minutes). Then put the battery back in, and see if you can get it into boot loader mode using the manual method discribed above.
-Chris
thank to Joey!!!!
we have life.. neither of us is exactly sure why but eventually it decided to talk so was reflashed and all ok!
ffelan said:
thank to Joey!!!!
we have life.. neither of us is exactly sure why but eventually it decided to talk so was reflashed and all ok!
Click to expand...
Click to collapse
no probs mate, hope all is ok, and hope u dont mess it again, lol...

I messed up my kaiser....How do i fix it?

I installed the Htcweatherdll.cab and my phone restart and now it doesn't not stop restarting. Is there a way to fix this?
Thanks
deizol1 said:
I installed the Htcweatherdll.cab and my phone restart and now it doesn't not stop restarting. Is there a way to fix this?
Thanks
Click to expand...
Click to collapse
Something similar to this happened to me, and a hard reset wouldn't work. I had to send it back to AT&T. Sorry man, hope you have better luck than I did.
deizol1 said:
I installed the Htcweatherdll.cab and my phone restart and now it doesn't not stop restarting. Is there a way to fix this?
Thanks
Click to expand...
Click to collapse
have you tried a hard reset, press down 2 softkeys and stick in reset button and release before letting go of the 2 soft keys. then follow on screen instructions ?
more info needed though ie can you access the bootloader, have you previously put a hard spl on your phone and if so which version.
god reading here on how to get phone back up and working http://forum.xda-developers.com/showthread.php?t=423486 and here too
i have the version from att
Ok now I got it to stop restarting but now its stuck
deizol1 said:
i have the version from att
Click to expand...
Click to collapse
From your response I'd say your best option if a hard reset does not work would be to see if you can access the bootloader screen ( press camera button and soft reset ) it looks like three colours on your phone. If you can then download an original rom for your phone and follow the instructions to place it on your phone.
Anyone have any better idea's
back in an hour let me know how you got on
That's the only conceivable idea probably. After you go into bootloader mode, flash the stock ROM and then if you have hardspl, install the custom ROM that you prefer.
Well i guess i can kiss all my #'s goodbye...you know what.....I think I want a custom rom...anyknow know where i can go to get a good one
deizol1 said:
Well i guess i can kiss all my #'s goodbye...you know what.....I think I want a custom rom...anyknow know where i can go to get a good one
Click to expand...
Click to collapse
You should always have your PIM either backed up or on your SIM.
Look in my sig for your request.
deizol1 said:
Well i guess i can kiss all my #'s goodbye...you know what.....I think I want a custom rom...anyknow know where i can go to get a good one
Click to expand...
Click to collapse
Dont go custom yet mate, try a stock rom and get it up and running first. Then take your time to read about soft / hard spl's and radios etc before diving in with a full custom rom. Believe me its worth it to understand everything first
AND READ THIS FIRST http://sakajati.com/forum/index.php/topic,3.0/prev_next,next.html#new
Thank you guys for your help....I downloaded the att rom from the htc website and i got my tilt running like new.....and I got all my #'s back ...looks like outlook does a good job hehehe
Time machine
deizol1 said:
I installed the Htcweatherdll.cab and my phone restart and now it doesn't not stop restarting. Is there a way to fix this?
Thanks
Click to expand...
Click to collapse
DOWNLOAD timemachine.cab, go back a few days, and don't make the same mistake.
Why do we get so many lame, I broke my XXXX because I'm a dolt, and expect the world have some magic panacea.
It really pisses me..
Sorry rant over.
Maybe I just hate kids, now where did I leave that gun....

Help me unbrick my phone

So i just updated to an SPL for a Hero ROM, and now i'm stuck on the t-mobile G1 screen, i can get to the console, but if someone can walk me through how to mount the SD card using ADB (from the very begining) it would be a great help. This way i can try to update the firmware, or resort back to the original radio/spl/firmware. I need a very easy to understand set of instructions, because every time i have tried to do something with ADB it never goes well.
all you need to do is re-flash your current rom your using no wipe needed.
Whats the command to do that, i've been trying to load the new ROM onto the SD card through the command prompt. and it doesn't seem to want to work.
Bassicly i use the adb push command to try and shove a ROM on to the SD card like this
adb push JAChero2.0r6.zip /sdcard/JACHero2.0r6.zip
and then i change the name to update.zip and it still applies the OLD SPL update.zip file i have in there.
Try removing the old update file first through the adb shell. I have run into a couple instances where it is doing what you are describing. I always found that removing the current file first will resolve it.
adb shell
# rm /sdcard/update.zip
# exit
adb push JAChero2.0r6.zip /sdcard/update.zip
Then try to flash the update through recovery.
Got it fixed, THANKS!
im stuck at g1 screen as well....what did you do to fix this?
Im stuck on G1 boot screen, cannot get into FBOOT or anything!
What can I do??
if none of the button combos work like home+power or camera+power or any others then you can either call tmobile and play dumb or have the sweetest paperweight at the office.
crpercodani said:
if none of the button combos work like home+power or camera+power or any others then you can either call tmobile and play dumb or have the sweetest paperweight at the office.
Click to expand...
Click to collapse
Will it cost me if I contact tmo?
I'll play it dumb, but when the phone ends up at some engineer, and they see what I've flashed on, will they just fix it, or report it to tmo? (as i've broken the t&c's!)
As much as having a paperweight sounds cool, I could really do with a phone!
BTW, thanks for your help!
IanVaughan said:
Will it cost me if I contact tmo?
I'll play it dumb, but when the phone ends up at some engineer, and they see what I've flashed on, will they just fix it, or report it to tmo? (as i've broken the t&c's!)
As much as having a paperweight sounds cool, I could really do with a phone!
BTW, thanks for your help!
Click to expand...
Click to collapse
If the phone won't boot using home + camera then they can't prove it's been rooted (unless they somehow read the nand...) so they should replace it for you without charge.. Same thing could happen if the battery was pulled during an over-the-air update.
they wont bother checking anything, just be sure it is bricked and your good. Most likely they just take it apart and jtag it or something like that. And if you got the phone from tmo and are with them then no its free.
AdrianK said:
If the phone won't boot using home + camera then they can't prove it's been rooted (unless they somehow read the nand...) so they should replace it for you without charge.. Same thing could happen if the battery was pulled during an over-the-air update.
Click to expand...
Click to collapse
crpercodani said:
they wont bother checking anything, just be sure it is bricked and your good. Most likely they just take it apart and jtag it or something like that. And if you got the phone from tmo and are with them then no its free.
Click to expand...
Click to collapse
Yep, it wont boot using any key-combo.
Its reading the NAND/using JTAG which is what I'd do (i work with embedded devices!).
I might say the battery died while the update was happening, gotta act dumb! (which I must be for managing to brick it in anycase, after all, Im a softy-eng!)
And I'll get a new phone! Or reconditioned?
Many thanks ppl!
Well.
If you manage to help this guy (http://twitter.com/r3nrutSite/) and the ppl on this thread (http://forum.xda-developers.com/showthread.php?t=309291) to JTAG the G1, please tell me.
I'm stuck with a bricked G1 here in Brazil.
Currently there is no way of bringin a g1 back to life short of giving it a heart transplant<new board>
see Brick Thread
Tp2 brick eny help??????
plis help
i was unlocking my phone (the HTC Touch Pro 2 <sprint>) and I was using a Diamond unlocker , but during the process there was a connection error and now my phone seems to be bricked. I can't get it to even turn on, get to a bootloader screen, or anything even remotely close.
The one odd thing that it does though, is when I connect it to my computer, it pops up and my computer recognizes there is a device there. In my Device Manager there is an unknown device called: Qualcomm CDMA Technologies MSM. I have tried every combination of two buttons, including holding down the reset button with all of them, but nothing gets me anywhere.
If anyone could help, I would really appreciate it. there's eny way to save it???
SHADE86 said:
plis help
i was unlocking my phone (the HTC Touch Pro 2 <sprint>) and I was using a Diamond unlocker , but during the process there was a connection error and now my phone seems to be bricked. I can't get it to even turn on, get to a bootloader screen, or anything even remotely close.
The one odd thing that it does though, is when I connect it to my computer, it pops up and my computer recognizes there is a device there. In my Device Manager there is an unknown device called: Qualcomm CDMA Technologies MSM. I have tried every combination of two buttons, including holding down the reset button with all of them, but nothing gets me anywhere.
If anyone could help, I would really appreciate it. there's eny way to save it???
Click to expand...
Click to collapse
Theres a app for that!
an app for recovery a htc tp2 brick
Ace42 said:
Theres a app for that!
Click to expand...
Click to collapse
really an app??
please tell me where i can find it
and what steps i must follow,
am desperatedm thank`s
SHADE86 said:
really an app??
please tell me where i can find it
and what steps i must follow,
am desperatedm thank`s
Click to expand...
Click to collapse
http://tinyurl.com/yayoq48
App used: Firefox

[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.

Fully Hard Bricked Moto G xt1072 (Help) DX

So i have a Moto g xt1072 wich i got second hand.. i got it into recovery mode and eventually got it working, but it was really unstable, so i wanted to reflash the stock rom, because it looked like the current one on the phone was corrupted (i was running android 6.0) (btw i have a xt1068 as my daily driver, but i want this to work again)
So i started flashing http://forum.xda-developers.com/moto-g-lte/general/stock-6-0-marshmallow-europe-reteu-t3338075 <-this
but i had errors and it was failing multiple times.. so i looked up some tutorials, and most of them were unlocking the bootloader at the beginning, so i was unlocking and locking the bootloader trying to get the commands to work,
then i found a tutorial wich coppyd all of the commands at once, so i tried that.. screen went black..
Wont boot into recovery, 3sec method or 120 sec method, and connects to my pc as QHSUSB_BULK
luckily i made a picture of the recovery when i tried to flash:
http://imgur.com/8avCk3T
I think i may need to blank flash, but im not certain..
I would also like to find the firmware for this phone that wont brick it..
Can anyone help?
Need more info?
Please just ask me, i will respond immediately
i dont care what i need to do.. even if i need to hardwire (because im really good at those finicky things)
Thanks for reading XD
Same issue here. I flashed a stock image and something must've gone wrong at some point
hamzahrmalik said:
Same issue here. I flashed a stock image and something must've gone wrong at some point
Click to expand...
Click to collapse
you probably also flashed the vootloader and the bootanimation, these are known to give problems, but ive foubd a test point on the pcb which brings the phone in a les hard bricked state, but ive yet to find a method to unbrick the phone..
ill keep you posted
ora69 said:
you probably also flashed the vootloader and the bootanimation, these are known to give problems, but ive foubd a test point on the pcb which brings the phone in a les hard bricked state, but ive yet to find a method to unbrick the phone..
ill keep you posted
Click to expand...
Click to collapse
Sorry could you please explain. How can a phone be less hard bricked. Thanks
Sent from my A0001 using Tapatalk
hamzahrmalik said:
Sorry could you please explain. How can a phone be less hard bricked. Thanks
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
okay, so there are different types of hardbricks, all act the same, but one is harder to unbrick than the other, there is qh usb bulk and qhas bulk with numbers behind it, search for force unbrick lg g2,
now the problem is, it should be easy to unbrick the phone at thsi point, but im not an expert in that and have no idea what to do now xD so i posted it on xda, but no one answered me.. xD hopefully this clears it up some more
ora69 said:
okay, so there are different types of hardbricks, all act the same, but one is harder to unbrick than the other, there is qh usb bulk and qhas bulk with numbers behind it, search for force unbrick lg g2,
now the problem is, it should be easy to unbrick the phone at thsi point, but im not an expert in that and have no idea what to do now xD so i posted it on xda, but no one answered me.. xD hopefully this clears it up some more
Click to expand...
Click to collapse
Oh ok I get you. Mines USB bulk 9000 or something i can't remmeber now
Sent from my A0001 using Tapatalk
ora69 said:
So i have a Moto g xt1072 wich i got second hand.. i got it into recovery mode and eventually got it working, but it was really unstable, so i wanted to reflash the stock rom, because it looked like the current one on the phone was corrupted (i was running android 6.0) (btw i have a xt1068 as my daily driver, but i want this to work again)
So i started flashing http://forum.xda-developers.com/moto-g-lte/general/stock-6-0-marshmallow-europe-reteu-t3338075 <-this
but i had errors and it was failing multiple times.. so i looked up some tutorials, and most of them were unlocking the bootloader at the beginning, so i was unlocking and locking the bootloader trying to get the commands to work,
then i found a tutorial wich coppyd all of the commands at once, so i tried that.. screen went black..
Wont boot into recovery, 3sec method or 120 sec method, and connects to my pc as QHSUSB_BULK
luckily i made a picture of the recovery when i tried to flash:
http://imgur.com/8avCk3T
I think i may need to blank flash, but im not certain..
I would also like to find the firmware for this phone that wont brick it..
Can anyone help?
Need more info?
Please just ask me, i will respond immediately
i dont care what i need to do.. even if i need to hardwire (because im really good at those finicky things)
Thanks for reading XD
Click to expand...
Click to collapse
So that link to another thread in XDA forum, I think I had a similar experience. I too have the XT1072 as I live in the UK. now here on XDA you have to be careful and ask 3 4 maybe 5 times before someone listens properly. I know it is hard for the devs with so many dumb noobs asking so many dumb questions, I include myself as a noob so no worries. Anyway to get to the point that link is not referring to our phone the XT1072. You should ignore LTE in your search criteria, it will always point you towards the 2015 model and believe you me all roms in my experience area very device specific. You need to simply put Moto G 2nd gen 2014 in search criteria when it comes to searching for custom recoverys and/or stock ROMS. The Titan.IMG is always a safe bet if I remember correctly, dont take my word for it, I have been known to have a memory like a sieve now and again, the problem with getting older, cache gets smaller and smaller, lol! Best of luck!
hamzahrmalik said:
Sorry could you please explain. How can a phone be less hard bricked. Thanks
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Read the beginning on this article: http://rootmyandroid.org/how-to-unbrick-your-android-device-the-ultimate-guide.html/
the bricked term is a common misconception for phones that still turn on..

Categories

Resources