Database Develop

Bricked? Im not sure of this situation...

So here's the deal.
it's a long story, but i happened in a short time.
I was unlocking my bootloader and stuff on my nexus one on my mac. using the boot loader.
I used the superboot to unlock it.
and so i succeed in that.
i didn't bother with the install-superboot-mac.sh thing.
i didn't know that by then.
so i went on to search about the cyanogenmod 7, and i can't get the radio refreshed. i read the article in the cm forum.
so, i saw this post somewhere,(...read hundreds of posts now)
that tells me to use the rom manager thing.
so i downloaded it, and i tells me that my phone is not rooted!
so i was wondering how this happened.
i searched online, and i found this post telling me to use that install.bat(which is for windows, mac is the one i mentioned above) thing after i unlock the bootloader.
i was a bit scared.
but i went on to the fast boot manu and i connect my computer,
i put the directory in, and then i threw the install-superboot-mac.sh thing in my phone, successful, so i rebooted my phone.
And after the first not-ANIMATED start up screen, which is the staying-X and the unlocked symbol at the bottom, the screen goes black.
i was not sure what happened. so i pullout the battery and booted it again.
same thing.
it was not until the third time i opened it and waited for it, i realized that it was my screen that's not working!
After the stable X, the system goes to the animated one, but my screen is blacked out, so i can't see.
The bottoms on the phone are still working , yet i can't see a thing!
I can still open the fastboot/bootloader screen, but after that, nothing!
the recovery don't work, it's just an android with the sign.
I'm very worried about this situation.
please reply to me!!
i really need help, since i know nothing about this.
I just thought that 2.3's cool and now i got this....
here's some info that might help,
i have the korean version of the phone, it was cheaper and stuff.
didn't notice a different except that there's no 3g?
i don't really know what's the deal with it.
but it seems to be special or something.
The phone is unlocked, but my computer fails to find it using the adb devices.
im not sure if my phone is usb debbuging.
probably yes.
Everytime i try to load the recovery, it tells me to wait for device.
I really need help!!

OK... so you might have messed up your firmware... no worries... get a custom recovery (like AmonRA recovery)... flash it using fastboot... pop in a custom ROM like CM... flash and reboot...

the thing is i can't load the recovery or the mods. so here's the problem

Do as Craig said.
Put phone into the bootloader screen. White screen with skateboarding androids.
Do your thing with fastboot.
Reboot directly into the freshly flashed recovery and install a ROM.
Read the wiki.
Sent from my Nexus One using XDA App

Read my signature, find a proper guide in Wiki ("Unroot / restore"), execute.
Next time, before you're trying anything, either find a good guide on the internet or try understanding what things actually do before you attempt them.

I've read the wiki, but is my phone compatible with the rom?
my phone's korean version..
im not sure if i can.
and i certainly can't afford another adversity.

reclusivenigma said:
I've read the wiki, but is my phone compatible with the rom?
my phone's korean version..
im not sure if i can.
and i certainly can't afford another adversity.
Click to expand...
Click to collapse
It will work just fine, your phone isn't bricked and will be working fine in no time if you follow the advice in the posts above.
Edit: Am I the only one who wants the word 'Bricked' explicitly defined for the xda forums?

and also, since my screen is out, im not sure of weather my back up data thing is on or not, and usb debugging also

i've tried the ROMs, but the three i tried don't work.
downloading more, but i doubt if there's difference.
the device doesn't tell me to install the update, instead it just goes back to the bootloader screen

i've tried the ROMs, but the three i tried don't work.
downloading more, but i doubt if there's difference.
the device doesn't tell me to install the update, instead it just goes back to the bootloader

...
K, they don't really work, after checking the rom, my phone just goes back to the screen that showed up when i pressed power and volumn down

Why do people insist on receiving their instructions on a golden spoon?
Do you think you're the first one ever that got his phone corrupted? Maybe the second?
Go to Wiki, download FRG33, proceed with instructions for PASSIMG method. PUT ATTENTION THAT YOU'RE NAMING THE FILE RIGHT!
These instructions have been given in 800000000 threads by now. Look for the thread about moving from Vodafone OS version to stock Google OS. Search the forum with the words "restore stock".

What exactly are you doing?
You have a few pieces of advice that will work, but you're not really giving any details about what you are actually trying...?
Here's the link to follow Jack's advice:
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_%26_Tutorials#Unroot_.2F_Restore_your_Nexus
Sent from my NookColor using Tapatalk

just if you want to know,
i've downloaded the frg33
and i HAVE NAMED it CORRECTLY!
YET, IT doesn'T WORK
im not a retard!
after the 2 min period of searching, which is step 7, my phone goes back to the same screen

CID incorrect!
Update Fail!
Do you want to reboot device?
<VOL UP> Yes
<VOL DOWN> No
this shows up a couple of times also

Why ask for help if you're not going to do what people tell you?
With a unlocked bootloadet flash a custom recovery.
Reboot DIRECTLY into that.
Wipe and flash any rom you want.
If you don't know how to do any of the above search or read the wiki.
Sent from my Nexus One using XDA App

As albundy2010 suggested - if you have the bootloader unlocked (I didn't notice that part in the OP), just follow the guide for unlocked bootloader - fastboot flash all the partitions on the device manually. The guide is in the same place, but a different one - this time use "for unlocked bootloader".

tHANKS man!
I was such a f-in idiot...
now i can finally boot into the recovery..

I got it.. thanks guys

It's a tough flashing world out there, hey rec
I am glad you got it working

[Q] having problems with installing honeycomb on my DS7

Hello Everybody!
So, the thing is that I bought a brand new DS7 from ebay recently, and it has Honeycomb in it, but about a week ago things went wrong -actually I'm not sure if it was good before. The tablet does not work on the proper way. First of all, I tried to install iGO on it, but it didn't let me to do it. So I can't install apps. And there are times when I can't connect it to the computer...and etc. I was wondering if it has a proper Honeycomb in it...so the point is that I decided to delete everything from it and reinstall the Honeycomb myself. I'm not very into these things, so it's a big effort for me to do this.
I have been searching for tutorials for 2 days. I think I found the right one somewhere here on this website. I've closed it unfortunately and it was opened yesterday and I cleared yesterday's history for some other reasons...so I can't open it again.
So the last time everything was ready, so was I, to do the installing. But, the comp. was searching for some APX files, probably drivers, but it didn't find it. So I couldn't continue the installation.
I've been looking for these drivers for hours, but haven't found anything. So I decided to register to this site, ask you, experts where to seek and what to do.
I lost so much time on this that I shouldn't have...
Thanks for your help in advance!
(Sorry for my English if it isn't understandable everywhere, I'm a non-native-speaker. Cheers! )

Now I'm about to restore the whole device following this (http://forum.xda-developers.com/showthread.php?t=1011654) tutorial. Hope it'll solve some of the problems.

raidon24 said:
Now I'm about to restore the whole device following this (http://forum.xda-developers.com/showthread.php?t=1011654) tutorial. Hope it'll solve some of the problems.
Click to expand...
Click to collapse
Dude, try not to dobblepost. Its quite better when you edit the first one.
(By the way im not a native english speaker to but i hope you understand what i mean)
Could you write down how far you come. At which step do you stop? And if the drivers are a problem, please post your Computer OS, like Windows or Linux or Mac.

I have solved the problem. Should I delete this thread somehow?

raidon24 said:
I have solved the problem. Should I delete this thread somehow?
Click to expand...
Click to collapse
No, you should post your solution in this thread. If someone has the same problem they may do a search and find this thread, and they can learn from you. Or if the solution was in another thread, post a link to that thread.

hah, okay The reason I didn't want to is because I think it's not a big deal. I have pushed the volume + and the Turn Off button then Factory Reset, and waited. Now everything's fine. The problem was, actually that I'd been doing...rather trying the reseting in a wrong way. I thought I should do it in the Settings/Privacy menu. But no. So It solved my problems. I didn't need to re-install Honeycomb as I'd thought the time I started this thread. I believed that the problem is in my HC, but fortunately no, so I'm going to sleep. Minden jót, srácok!

[Q] Forgot USB-debugging downgrading

Hi!
This is my first post an I hope I did put it on the right place and I havent found any other post that really matches my problem.
Anyway, I was so happy for being able to bring back stock rom on a rooted SGS2 I9100 who didnt worked proper with its root. In this case, no USB-debugging were necessary.
After this mission I felt ready to try to downgrade the SGS Advance I9070 from stock Jelly Bean to Stock Ginger Bread by mainly following one of all those tutorials about how to do it. And I know its said - enable USB-debugging.
But as I were interupted by my wife just before I were going to proceed, I totally forgot it when I finally went back to my work of downgrading. As I were a bit stressed, I just connected the phone to Odin and slammed the PDA-button like I did with the SGS2. It went smooth all the way through Odin and the green PASS showed up. But when the phone were about to boot up it stuck at the Samsung-logo. Its in a bootloop. After a short time of wondering about what went wrong, it struck my head I forgot to enable USB-debugging. Amen!
So, I forgot debugging while running JB-stock to downgrade to GB-stock. The only thing I can reach now is download-mode except the bootloop Samsung start interface. Its probably occured because I forgot enable debugging, right? And does it mean this device is bricked for real or is there anyway to bring back life?
Best regards // emsoh

emsoh said:
Hi!
This is my first post an I hope I did put it on the right place and I havent found any other post that really matches my problem.
Anyway, I was so happy for being able to bring back stock rom on a rooted SGS2 I9100 who didnt worked proper with its root. In this case, no USB-debugging were necessary.
After this mission I felt ready to try to downgrade the SGS Advance I9070 from stock Jelly Bean to Stock Ginger Bread by mainly following one of all those tutorials about how to do it. And I know its said - enable USB-debugging.
But as I were interupted by my wife just before I were going to proceed, I totally forgot it when I finally went back to my work of downgrading. As I were a bit stressed, I just connected the phone to Odin and slammed the PDA-button like I did with the SGS2. It went smooth all the way through Odin and the green PASS showed up. But when the phone were about to boot up it stuck at the Samsung-logo. Its in a bootloop. After a short time of wondering about what went wrong, it struck my head I forgot to enable USB-debugging. Amen!
So, I forgot debugging while running JB-stock to downgrade to GB-stock. The only thing I can reach now is download-mode except the bootloop Samsung start interface. Its probably occured because I forgot enable debugging, right? And does it mean this device is bricked for real or is there anyway to bring back life?
Best regards // emsoh
Click to expand...
Click to collapse
LOL...:laugh: Wives will remain Wives!
The device is Soft Bricked and can be resurrected..did you follow this procedure: http://forum.xda-developers.com/showthread.php?t=2195673 ?

arneldna said:
LOL...:laugh: Wives will remain Wives!
The device is Soft Bricked and can be resurrected..did you follow this procedure: http://forum.xda-developers.com/showthread.php?t=2195673 ?
Click to expand...
Click to collapse
Haha.. Well, I had to drive her to the shop and that was enough to make me lose my patience of remembering important rules just because I had to go with other important rules. Like the gentleman I am. :fingers-crossed:
Thanx for reply. It makes me glad you do believe its possible to fix this issue. The link you showed is on of those I been looking at before I got started. But after a lot of comparing between several links from i-net, I decided to go with the procedure that the majority declared. For example, in this link its said "re-partition" must be ticked in. The other guides said not. Only "reboot" and "time-reset" to be ticked in.
The stock firmwire I downloaded were from some address connected to Samsung. It means there were only one file with all included just to insert in the PDA. Now, afterwards..I do understand it isent that hard to fill in 3 lines myself instead of one. But it seemed simplier with only one at that time. As I am a newbie about changing software in phones, I were ready to make mistakes but not this mistake and I really dont know what guides who are the best to go with.
Do you think it will make any difference if I go with your link and try again?
Remember, the phone were not rooted. Im really not sure, but I think I read somewhere that if debugging are not enabled on official kernel, theres no way back because cant reach debugging in any way. But I hope its not true.
Now, as far as I understand in my case...what I did was to erase the operation system I had (stock 4.1.2) and filled it up with (stock 2.3.6) but it only reached the gates and not the internal of the phone. It means there are no operating system at all?
Then why Odin shows PASS? And if no communication files can reach the phone, how is it possible that the counter now shows the phone has been rooted? Yes, I tried to root it today and Odin showed PASS again. And as the counter counts, it must mean the phone is not 100% blocked from communication even without debugging enabled?
But still the phone act as described earlier. Only Samsung-logo, bootloop and I can only go forward to download-mode.
:crying:

emsoh said:
Haha.. Well, I had to drive her to the shop and that was enough to make me lose my patience of remembering important rules just because I had to go with other important rules. Like the gentleman I am. :fingers-crossed:
Thanx for reply. It makes me glad you do believe its possible to fix this issue. The link you showed is on of those I been looking at before I got started. But after a lot of comparing between several links from i-net, I decided to go with the procedure that the majority declared. For example, in this link its said "re-partition" must be ticked in. The other guides said not. Only "reboot" and "time-reset" to be ticked in.
The stock firmwire I downloaded were from some address connected to Samsung. It means there were only one file with all included just to insert in the PDA. Now, afterwards..I do understand it isent that hard to fill in 3 lines myself instead of one. But it seemed simplier with only one at that time. As I am a newbie about changing software in phones, I were ready to make mistakes but not this mistake and I really dont know what guides who are the best to go with.
Do you think it will make any difference if I go with your link and try again?
Remember, the phone were not rooted. Im really not sure, but I think I read somewhere that if debugging are not enabled on official kernel, theres no way back because cant reach debugging in any way. But I hope its not true.
Now, as far as I understand in my case...what I did was to erase the operation system I had (stock 4.1.2) and filled it up with (stock 2.3.6) but it only reached the gates and not the internal of the phone. It means there are no operating system at all?
Then why Odin shows PASS? And if no communication files can reach the phone, how is it possible that the counter now shows the phone has been rooted? Yes, I tried to root it today and Odin showed PASS again. And as the counter counts, it must mean the phone is not 100% blocked from communication even without debugging enabled?
But still the phone act as described earlier. Only Samsung-logo, bootloop and I can only go forward to download-mode.
:crying:
Click to expand...
Click to collapse
Don't worry - as long as you have access to download mode you are fine :good:
I am not sure as I never downgraded to GB myself, but from my understanding of posts in here it is partitioning issue.
JB got different sizes or mount points (forgot exactly) of key partitions and that is what is wrong here - it cannot find some components to finish booting.
re-partition is the main thing here.
Get file from this guide.
Key point is:
9)Hit on PIT button and select the PIT file extracted from the downloaded package in first step above (GT-I9070_EUR_XX_8G.pit).
You should be able to use your 1-file-ROM and get it working, as long as you use .pit and tick re-partition.
Worst case scenario - flash JB again (no re-partition needed) and it will be working as before ;]

th3cr0w said:
Don't worry - as long as you have access to download mode you are fine :good:
I am not sure as I never downgraded to GB myself, but from my understanding of posts in here it is partitioning issue.
JB got different sizes or mount points (forgot exactly) of key partitions and that is what is wrong here - it cannot find some components to finish booting.
re-partition is the main thing here.
Get file from this guide.
Key point is:
9)Hit on PIT button and select the PIT file extracted from the downloaded package in first step above (GT-I9070_EUR_XX_8G.pit).
You should be able to use your 1-file-ROM and get it working, as long as you use .pit and tick re-partition.
Worst case scenario - flash JB again (no re-partition needed) and it will be working as before ;]
Click to expand...
Click to collapse
Ok, it makes me a bit more calm and Im starting to believe a bit, theres a way back for the phone to rise again. So you mean it might not be the failure of missed debugging, instead the critical main thing can be re-partiton?! It sounds very possible based on what you said.
The thing now is, ofcourse I would be satisfied if my first plan come true. But right now I really dont care what version it´ll be running, rooted or not. I only want it to act like a smartphone again n matter what´s installed. So I will go with your advise and test it one by one.
Thanx so far! To be continued..

SOLVED Forgot USB-debugging downgrading
I must admit I didnt really believed it wud work even I hoped it wud do. Before I started the new operation I gave it the chances 75% negative and 25% positive. But I was so wrong.
It really passed!!
Im so thankful for the support. To arneldna who made me reconsider this current version and tutorial for firmware downgrade. And to th3cr0w who explained and really pointed out the missing spot in my failure of action during the installing process.
The solution - Just to be sure, I followed the tutorial exactly. When it rebooted it showed up not to be my country region so I did it again with my nordic region all-in-one tar-file. This time just to be safe, I enabled usb-debugging and also unknown sources. Idk if it had any use but just in case of. And Voila..back to my region and everything seems to be as it was the first time I started up the phone when it was new last summer. After that I did a factory reset which I learned is useful to do.
As this was only one of my childrens phones, I actually got 3 more of the same to downgrade to work smooth again. But now I learned another lesson. I hope!
THANX A LOT to both of you! :good:

emsoh said:
I must admit I didnt really believed it wud work even I hoped it wud do. Before I started the new operation I gave it the chances 75% negative and 25% positive. But I was so wrong.
It really passed!!
Im so thankful for the support. To arneldna who made me reconsider this current version and tutorial for firmware downgrade. And to th3cr0w who explained and really pointed out the missing spot in my failure of action during the installing process.
The solution - Just to be sure, I followed the tutorial exactly. When it rebooted it showed up not to be my country region so I did it again with my nordic region all-in-one tar-file. This time just to be safe, I enabled usb-debugging and also unknown sources. Idk if it had any use but just in case of. And Voila..back to my region and everything seems to be as it was the first time I started up the phone when it was new last summer. After that I did a factory reset which I learned is useful to do.
As this was only one of my childrens phones, I actually got 3 more of the same to downgrade to work smooth again. But now I learned another lesson. I hope!
THANX A LOT to both of you! :good:
Click to expand...
Click to collapse
Glad to know you fixed it.. Appreciate your patience and efforts... :thumbup:
You don't care where I sent it from....!

[Q] Computer won't recognize device after flash

I am a beginner at this, so bear with me. I had an old HTC One lying around that was somewhat in a non-working state. Not as a phone anyway as it constantly lost service. Someone told me that it might perhaps be a software issue and if I rooted it and used a different ROM, it could fix my problem. So, for the first time, I gave it a shot. I tried a bunch of things, followed many tutorials, but I couldn't gain s-off on the device. Finally, someone said since my hboot was version 1.57, I would need to use sunshine to accomplish my goal. I did so and it worked. So now I followed another tutorial which showed how to make it a google play edition device. So I flashed the RUU and it failed the first time around. I tried again as the tutorial said I would have to only to get another error. My computer said it was waiting for a device. Basically my problem is that now when I'm in fastboot mode, my computer won't recognize it. When I boot it normally however, it acts like usual. I've visited other suggested threads on these forums, but to no avail. I've tried other chords, I've updated drivers, I've gone into the device manager and did just about everything suggested. So I've come here for one last try. If anyone could help that would be greatly appreciated.

Sir,
Please wait until mods will move this thread to the device specific forum.
For reply or more questions please register an account on XDA forums.
Stand by
Good luck

Thank you for your assistance in moving my thread to the correct location. I'd also like to note that I read quite a few articles where people seem to have the same problems as I have or have had, but none of them seem to help. Just so you know I didn't run straight for the post option and actually put some effort into finding my solution before hand.

Unable to unlock bootloader due to errors within ADB and fastboot

Hello,
this is my first thread/post on this forum, if I did anything wrong please don't be super harsh and inform me to what to do better, thanks.
So why am I asking for help anyways you may ask, well I had my old Xperia Z1 laying around here for quite a while now and wondered if I could do anything productive with it.
So I came up with the idea to install a CFW like Lineage OS or something else.
This is not my first rooted and cfw phone but the first one what gives me nightmares and a headache.
So after reading all of the nice guides how to root it and how to unlock it, nothing of them is working for me, most of the threads have missing files which I cannot find on google or other just simply won't work for me.
First of all, I have rooted my phone via KingRoot in the meantime since the other methods where not working either.
I have turned on usb-debugging and also allowed installation from unknown sources.
And there we start with the first problem, downloaded the google SDK and installed all adb things I needed, did not work, then I tried it from the official sony website, downloaded the usb-driver folder and tried to install it manually, won't work either, because the device manager always gave me error code 10 "device cannot be started", I tried different sources and even die google studio thing and everything ended up with the same result.
Same error code even when I tried to activate fastboot on my phone by pressing down the volume up button, pluging the usb cable in, and yet again the same error message for this device too.
I am using windows 10 and never had such problems before with sony devices.
I hope someone of you can help me out to find a solution, if you need any further information, just let me know.

Did you solve this?
I have the same problem

snailer said:
Did you solve this?
I have the same problem
Click to expand...
Click to collapse
This may sound stupid or ridiculous, but yes I managed to work it out and was able to install the CWF on my phone which is working perfectly fine.
Since nobody was willing to help me I just skipped the part where I wanted to post my solution but yeah, this may help you too.
So what did I do? Simply I stopped using Windows 10 for this project, I just used one of my older PC's which still had Windows 7 Ultimate on it.
I just rooted the phone via KingRoot, since it was the only solution what kinda worked out for me, then I was able to install all needed SDK, fastboot and ADB files on my PC and was able to use the ones from the Sony site itself this time and after plugin in the phone to the PC, it installed everything else what was needed for the device manager.
After that was done with no error I was finally able to unlock the phone via the command which you can find also on the Sony website.
If you find this helpful or need any extra information just let me know, maybe I can help you then. Oh and if you found out a solution for you what worked, would be nice to hear that too.
Greetz