Hi
I was rooting my phone today (not for the 1st time). I had root, and needed to use a few commands in terminal. I updated to Jesus Freak's 1.5 software, and I am now stuck in the boot screen (Android).
I'd appreciate help. I can't access my SD...
Anyone? It's late, i've got a busy day tomorrow and I need my phone to work... i'd really appreciate it...
Ok, it got me through somehow, but it says i'm on a dev phone???
paddlesmack said:
Ok, it got me through somehow, but it says i'm on a dev phone???
Click to expand...
Click to collapse
yes because you flashed Jf's ADP image......
Related
Problem solved
I'm assuming you used icoke to unlock first?
mssmison said:
I'm assuming you used icoke to unlock first?
Click to expand...
Click to collapse
Yeah i did, i relocked it then unlocked it with an older version of coke I had and it seems to be working now. Freaked me out though >.<
Same problem....
Hey i seem to be having the same problem with my phone, was wondering if u could give me the steps u used and what relocker u used and unlocker. I would greatly appreciated!!=)
Why do you people necro post? Make a new thread with your problem. I can garuntee you whatever he did in march is not going to work for you now.
My friend flash his rogers g1 to android 1.0 with 1.22 radio and spl .95 something or the other thinking it would give him access to paid apps. in trying to get back to donut 1.5, he flashed cm 1.4 recovery then flashed update zip via recovery console using cyan wiki info:
http://wiki.cyanogenmod.com/index.p...ogers_Dream_EBI1_to_CyanogenMod#Prerequisites.
Now phone only boots to t-mobile image. no recovery or fastboot. Can somebody please help or is phone bricked?
If no recovery or fastboot... Most Likely it's bricked
not only is it probably bricked, you posted in the wrong section
jad011 said:
not only is it probably bricked, you posted in the wrong section
Click to expand...
Click to collapse
Well he said it was urgent.
Wrong Section BTW
you have a new paperweight....im so not jealous ha
Ace42 said:
Well he said it was urgent.
Click to expand...
Click to collapse
Lol sucks for you man, gotta read the instructions!
If it's booting to the tmobile screen it sounds like it might be soft bricked, there's a thread here somewhere which might help.
vegaman said:
If it's booting to the tmobile screen it sounds like it might be soft bricked, there's a thread here somewhere which might help.
Click to expand...
Click to collapse
the rogers dream does not have a g1 screen dude... it has a rogers screen.. and there's no such thing as a "rogers g1"
when you turn on the phone, it stays at t-mobile boot screen. and its not my phone. i had a magic, sold it, waiting for nexy . I was trying to help my friend. is it possible threw adb on comp to flash recovery image?
jfive74 said:
when you turn on the phone, it stays at t-mobile boot screen. and its not my phone. i had a magic, sold it, waiting for nexy . I was trying to help my friend. is it possible threw adb on comp to flash recovery image?
Click to expand...
Click to collapse
Won't be able to use adb because you can't get to recovery won't do adb otherwise :/
PS: You can always throw it at the person who's phone it is and run like hell lol
ok so i got my hands on my sisters old G1 and it was unrooted and with rc30.
so i was able to downgrade it to rc29, flash it with RA recovery 1.7.0, and i was applying the the spl next. i booted into recovery and flashed the spl, and when i rebooted the g1 i just got suck at the tmobile g1 screen, i left it there for like 10 minutes thinking its gonna do its thing but it was still stuck there.
i pulled the battery out and pressed home and the power button, and it still didnt wanna go into recovery. so i pulled the battery again. so pressed and held the camera button and power button and it booted into the g1 screen instead!
so at this point i think i bricked it since im just stuck at the g1 screen and cant do nothing from there and i wanted a 2nd opinion to confirm it, or for a possible solution.
im thinking i messed up with the spl, but the one i have DL is the same one i used with my old G1 and its still kicking some (this one has a problem with the flex ribbon cable i believe, but completely usable.)
Im pretty sure when a phone is bricked, you cant even boot your phone, so im pretty sure ur phone is not bricked.
sorry, idk how to fix this, but im sure someone does.
You have to flash a rom, of coursebit would get stuck at g1 screen bcuz it had no direction(no rom)
Sent from my HTC HD2
the situation is you can get into hboot but not recovery nor system，right?
you could flash radio/spl via fastboot ,then flash recovery, rom at last.
read this thread:http://forum.xda-developers.com/showthread.php?t=532719,try to fix it
edward0119 said:
the situation is you can get into hboot but not recovery nor system，right?
you could flash radio/spl via fastboot ,then flash recovery, rom at last.
read this thread:http://forum.xda-developers.com/showthread.php?t=532719,try to fix it
Click to expand...
Click to collapse
no i cant access recovery, or hboot.
when i hooked it up to the computer hoping that it might recognize it, nothing happened either when i tried to boot into hboot, or recovery.
so ive been doin some more digging into the internet and yep i did end up bricking it.
looks like im gonna perform some phone operation between the two g1s to have a fully working one.
so pressed and held the camera button and power button and it booted into the g1 screen instead!
you said this last day,it doesn't work now?
edward0119 said:
you said this last day,it doesn't work now?
Click to expand...
Click to collapse
no it doesnt.
i have no access to hboot, or recovery. and it doesnt get recognized by my computer if i try to have it hooked up with the usb, so i cant even use adb or nothing.
so like i said, i could pretty much confirm myself that i bricked it. so right now im like phoneless because my original g1 has an issue with it not showing nothing if the keyboard is CLOSED (yes closed, not open! lol) and it ended up closing on me when i tossed it in my bed (doh!)
damm that sucks man.. sorry for your loss lol
ldrifta said:
damm that sucks man.. sorry for your loss lol
Click to expand...
Click to collapse
haha its alright, only option right now is phone operation with the two g1s i have, but i need to buy a torx screwdriver for it since the one i got is the wrong size.
but its not such a bad thing because ive been hearing that i might end up getting a new HTC phone as a graduation present. so heres to hoping thats true! lol
I guess it is bricked,maybe it can be fixed by a serviceman
Well seeing it's screwed lol try out JTAG used it before to unbrick a phone once ^^ that should be a solution for you
xillius200 said:
Well seeing it's screwed lol try out JTAG used it before to unbrick a phone once ^^ that should be a solution for you
Click to expand...
Click to collapse
yeah i was looking into that, but idk it seemed wierd for me.
but last night i opened up the g1s and replaced the motherboards from eachother. and now i got a working g1!
Hey guys, ive been trying to root an HTC First that i got recently after my rooted one battery fried it. now I cant seem to get the bootloader unlocked with HTCDev. Getting an error 173 and not sure what it means. Any help would be nice, even if its telling me it cant be done. thanks in advance!
It's perfectly doable. Choose "All Other Supported Models". Seems like error 173 is a website error, perhaps wait for a less busy time and try again.
oh so by that do you mean later at night?
Stoofer98 said:
oh so by that do you mean later at night?
Click to expand...
Click to collapse
what he means, is that there is only a certain amount of processes the server can do at any given moment, guess you got unlucky lol
Hi
I recently tried to root my phone from this guide: devs-lab.com/root-samsung-galaxy-s7-s7-edge
I followed the instructions and flashed this file from ODIN:
Samsung_G930x_QC_Rooted_BOOT.TAR
The file transferred ok and when the phone started rebooting it just stopped with a fault message on the screen.
Now the phone is stucked and i can't get contact with Odin. Odin recognizes the phone on the port but i cant flash to the phone.
The only way i have a chance to install on the phone now is with SD-card, because i am able to get to the recovery mode.
But when i try to install new stockware i just get signature failed message.
Does anyone know how i can get out of this mess ? I know its possible to turn of the signature check, but i cant get any options like this in the menu ..... BTW the phone is a G930F
I would really appreciate all help !
Thanks
Tom
Tom-72 said:
Hi
I recently tried to root my phone from this guide: devs-lab.com/root-samsung-galaxy-s7-s7-edge
I followed the instructions and flashed this file from ODIN:
Samsung_G930x_QC_Rooted_BOOT.TAR
The file transferred ok and when the phone started rebooting it just stopped with a fault message on the screen.
Now the phone is stucked and i can't get contact with Odin. Odin recognizes the phone on the port but i cant flash to the phone.
The only way i have a chance to install on the phone now is with SD-card, because i am able to get to the recovery mode.
But when i try to install new stockware i just get signature failed message.
Does anyone know how i can get out of this mess ? I know its possible to turn of the signature check, but i cant get any options like this in the menu ..... BTW the phone is a G930F
I would really appreciate all help !
Thanks
Tom
Click to expand...
Click to collapse
Which fault message are you receiving?
Sent from my SM-G930P using Tapatalk
POWerSUrgeSW3 said:
Which fault message are you receiving?
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse
Hi,
I dont remember exactly the fault message because my phone has been sent to service. But i will get it back in a couple of days. Then i will tell you the entire message. But is was something about kernel fault....
The service center says i have to replace the main board on the phone which cost almost the same as a new phone....
But i'm sure the main board is not broken...
Tom
Tom-72 said:
Hi,
I dont remember exactly the fault message because my phone has been sent to service. But i will get it back in a couple of days. Then i will tell you the entire message. But is was something about kernel fault....
The service center says i have to replace the main board on the phone which cost almost the same as a new phone....
But i'm sure the main board is not broken...
Tom
Click to expand...
Click to collapse
Blah that's never good. Though I don't always trust things HAVE to be replaced at the hardware level. But it is what it is. Hopefully when you get it back all will be working for you! Unless it was just a bad chip, failing at the same time you were trying to write the new files to memory?
Sent from my SM-G930P using Tapatalk
POWerSUrgeSW3 said:
Blah that's never good. Though I don't always trust things HAVE to be replaced at the hardware level. But it is what it is. Hopefully when you get it back all will be working for you! Unless it was just a bad chip, failing at the same time you were trying to write the new files to memory?
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse
Well....
Actually i'm hoping to fix the phone withouth replacing the main board since it is so expencive.
So i asked them to return it withouth replacing. Because as long as i can get the phone in recovery mode its not broken. I just need to get pass Samsungs signature verification somehow... Then i can install new firmware...
Still hoping to get help. I will post the error message as soon as i get the phone back,
Thanks so far
Tom
Tom-72 said:
Well....
Actually i'm hoping to fix the phone withouth replacing the main board since it is so expencive.
So i asked them to return it withouth replacing. Because as long as i can get the phone in recovery mode its not broken. I just need to get pass Samsungs signature verification somehow... Then i can install new firmware...
Still hoping to get help. I will post the error message as soon as i get the phone back,
Thanks so far
Tom
Click to expand...
Click to collapse
I think I did the same thing when I first got the Phoenix, and did not research and do not turn the OEM Unlock feature on. I messed up things and through a lot of reflashing and panic searching, got mine to come back.
I since have seen others post issues that sound horrible but have been recoverable. We'll help you try to figure it out once you get the phone back.
Sent from my SM-G930P using Tapatalk
POWerSUrgeSW3 said:
I think I did the same thing when I first got the Phoenix, and did not research and do not turn the OEM Unlock feature on. I messed up things and through a lot of reflashing and panic searching, got mine to come back.
I since have seen others post issues that sound horrible but have been recoverable. We'll help you try to figure it out once you get the phone back.
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse
Hi, i finally got my phone back.
Been trying different things like installing new firmware by using the SD-card. And also by using ADB, since the phone allows me to install software through ADB.
But no matter what i do the phone tells that signature verification failed.
I think one fault i did when installing the twrp custom recovery from ODIN i forgot to press the key combo and it started up with the original bootloader. Then it got stuck with the error screen i told you about.
I have uploaded a picture of the error message below.
If anyone knows how to get by the signature verification test then maby i could be able to install new firmware....
Thanks again, i will be grateful for any tips that could help me !
Best Regards
Tom
Tom-72 said:
Hi, i finally got my phone back.
Been trying different things like installing new firmware by using the SD-card. And also by using ADB, since the phone allows me to install software through ADB.
But no matter what i do the phone tells that signature verification failed.
I think one fault i did when installing the twrp custom recovery from ODIN i forgot to press the key combo and it started up with the original bootloader. Then it got stuck with the error screen i told you about.
I have uploaded a picture of the error message below.
If anyone knows how to get by the signature verification test then maby i could be able to install new firmware....
Thanks again, i will be grateful for any tips that could help me !
Best Regards
Tom
Click to expand...
Click to collapse
Good NEWS !!!!!
I managed to get the phone working again...
What i did was:
Holding the volume down, home and power button at the same time. When the phone went black i plugged in the USB cabel from the computer.
The error message came up 2 - 3 times but i kept holding the buttons.
Eventually it went into download mode and i used ODIN to flash the firmware...
I hope this could solve the problem also for others facing similar issues.
Thanks to BWolf56 who posted in a forum here. His tips fom 2011 .... helped me.
Regards
Tom
Tom-72 said:
Good NEWS !!!!!
I managed to get the phone working again...
What i did was:
Holding the volume down, home and power button at the same time. When the phone went black i plugged in the USB cabel from the computer.
The error message came up 2 - 3 times but i kept holding the buttons.
Eventually it went into download mode and i used ODIN to flash the firmware...
I hope this could solve the problem also for others facing similar issues.
Thanks to BWolf56 who posted in a forum here. His tips fom 2011 .... helped me.
Regards
Tom
Click to expand...
Click to collapse
Great to hear... Good luck from here on out!
This is a good sign not to listen to tech support. They don't know, or mess with this stuff, as much as us!
Happy flashing and hope no more scares from here on out...
Sent from my SM-G930P using Tapatalk