Hello I'm new around all this flashing thing.i heard of rooting an adroid and all the benefits it brings. I decided to give it a try. I own a galaxy infuse 4G.(sgh-i997).i did sone research, got the requisite files. I booted into recovery mode in followed the instructions given to me. For some reason i could not explain a yellow text appeared saying "signature verification failed "... I spent a couple of hours trying to gt past this barrier.. .found an app which could root my phone without going through recovery mode(framaroot).But i had to get rid of yellow tedt issue.. I did more research and found that the signature verification issue can be resolved.I followed the steps painstakingly; i mounted my system, replaced the old recovery file with the new one I'd downloaded,boot into recovery mod and flash the CWM file.. I tried to flash de CWM but this time i wasn't blocked by "signature verification ".My recovery mode kept restarting anytime i try flashing de CWM. I reset the phone at that instance thinking everything was back to normal.I used the phone for a couple of minutes; signing into my Google account and all that i just left the phone to cool down for a while to my surprise the phone had restarted without my authorization..At first i thought maybe it was me but the phone kept restarting anytime the backlight goes off until i plugged my charger in, the restarting stopped, i plugged it out to c what would happen, the restarting came back.. I friend suggested i flashed it. But i dont really know. Could that help. Please if you have any other suggestion let me know. I need all the help i can get.. THANKS
Hi
Thanks for writing to us at XDA Assist. It's a bit difficult to know what's going on with your device without you providing exactly what you've done to it, saying "I followed some instructions" is like saying nothing at all. When requesting help it's best to provide names/links to everything you've done to the device otherwise troubleshooting is virtually impossible. Anyway, I'd suggest you follow the directions in the below thread to get your phone back to stock.
[ODIN][UCLB3] UCLB3 Unbrick - Return to stock - Working PIT included
Good luck!
No response in two days, thread closed.
Related
I tried to upgrade my brothers samsung galaxy gio with a leaked version of it's 2.3.4 upgrade via "Odin".It kinda got stuck in the process and following the guide for it I removed the battery (it said to remove the battery if it stuck at a process for more than 10 minutes). After that when I tried to power it up it got stuck with an image of a phone and a pc connected with dots and a caution mark in between. For extra info recovery mode doesn't open but the download mode does. And I have tried to upgrade it a few times but gets stuck at the process named "ididb download"or something like that.
Is the phone bricked?????? Plz reply quick.
Hi,
Don't worry: as long as you can turn the phone on you should be OK, it's only a soft brick . Have you tried going in download mode again, and reflashed another ROM or even the one you attempted? Got evering right? OPS? Evering you must tick? Re-read the whole tutorial cause generally people mess up because they don't pay enough attention ^^
P.S. At least a million threads exist for this, you obviously haven't looked far before posting..
I wanted to share my knowledge and experience from the past 2 days. Most of the help came from guides and posts on this forum so I wanted to give that back.
We were trying to root the SGS4G and because we're noobs we made the mistake of thinking it was a Vibrant. Got a Vibrant ROM and tried to flash it though Odin WITH re-partition checked. Everything we read said if you do either one of these things, you will brick your phone.
Sure enough we bricked the phone. It was trying to boot into the Vibrant ROM but was getting stuck on the word 'Vibrant' and then showing a whole lot of weird colored pixels. We then learned we'd made a massive mistake and that the phone wasn't a Vibrant after all.
We got a stock ROM for SGS4G and started trying to push them through Odin. Faced countless FAILS and freezes and finally it took us to the Recovery Mode and we tried the Restore option. It booted into a crippled SGS4G ROM. When it booted, it vibrated every 10 seconds or so and it had a null IMEI and unknown baseband.
We tried following a guide that wanted to change some text in the nv_data.bin but the numbers we were meant to be editing (0018810?) didn't exist in our nv_data.bin. So that didn't work for us.
In the meantime we tried to flash the stock ROM in Odin but kept getting FAILs and Freezes. With this step we lost even the crippled operating system and couldn't reach anything except the 'phone --!-- computer' screen. Luckily, this acts the same as download mode, so not bricked. We kept trying to push the stock SGS4G stock ROM (Froyo 2.2) several times and failing.
At one point we got a completely black screen, wouldn't turn on. Bricked again. We found this post on RootzWiki and it worked for us that time and brought it back from the black screen to download mode http://rootzwiki.com/topic/1820-how-to-unbrick-your-sgs4g/
Somehow we ended up at this guide here on XDA for fixing the "null/null" IMEI http://forum.xda-developers.com/showthread.php?t=1142829
We followed that guide. When you add the PIT file it automatically checks 'Re-Partition' in Odin, we didn't uncheck it. Bricked again. It was stuck on the Samsung logo and when we tried to get to download mode it got stuck on a black screen with the loading circle/lines and 2 computers were giving 'The USB device has malfunctioned' when we plugged it in. The unbrick guide above (RootzWiki) didn't help this time. We tried restarting the computer, let the phone rest without battery for half an hour, held power button for a minute without battery, still nothing.
Finally I accidentally pressed the power button (rather than the volume buttons to get into download mode) and it went to the samsung logo (as expected) and after that I was able to get into download mode. The key to this I think is to keep on trying powering on normally then try download mode over and over and eventually it should get unstuck and the computer should recognize it again.
Once I had it back in download mode, I followed this guide again BUT!!! I made sure to un-check re-partition and I did not check "Phone EFS Clear" (because I had tried that already before it was bricked and wanted to see if a straight ROM would work first). Everything worked perfectly, I got my IMEI and Baseband back, without modifying anything.
I don't know if this was a miracle, or if any of it will work for anyone else, but the moral of the story is don't give up even if you've done the absolute worst possible thing. I don't even think hardbrick exists on this phone after everything we were able to save it from.
Cheers
Hardbricks do exist on this phone but you have to try really hard to do it. A few people have managed it. Way to stick with it and recover your phone. I've done that more times than I can count.
hechoen said:
Hardbricks do exist on this phone but you have to try really hard to do it. A few people have managed it. Way to stick with it and recover your phone. I've done that more times than I can count.
Click to expand...
Click to collapse
I didn't feel like i really hard bricked it until i saw the USB computer connection error "device pluged in malfunctioned" in more than one PC.
Then i really felt like its a hardware BIOS chipset level problem now but man...
That story cracked me up. That is exactly why I spend days reading before I even root my phone. I made the mistake one time on my old G1 and it could not be revived.
Congrats on getting it working. (especially without flooding the q&a with redundant questions that have been described in detail several places )
hani1400 said:
I wanted to share my knowledge and experience from the past 2 days. Most of the help came from guides and posts on this forum so I wanted to give that back.
We were trying to root the SGS4G and because we're noobs we made the mistake of thinking it was a Vibrant. Got a Vibrant ROM and tried to flash it though Odin WITH re-partition checked. Everything we read said if you do either one of these things, you will brick your phone.
Sure enough we bricked the phone. It was trying to boot into the Vibrant ROM but was getting stuck on the word 'Vibrant' and then showing a whole lot of weird colored pixels. We then learned we'd made a massive mistake and that the phone wasn't a Vibrant after all.
We got a stock ROM for SGS4G and started trying to push them through Odin. Faced countless FAILS and freezes and finally it took us to the Recovery Mode and we tried the Restore option. It booted into a crippled SGS4G ROM. When it booted, it vibrated every 10 seconds or so and it had a null IMEI and unknown baseband.
We tried following a guide that wanted to change some text in the nv_data.bin but the numbers we were meant to be editing (0018810?) didn't exist in our nv_data.bin. So that didn't work for us.
In the meantime we tried to flash the stock ROM in Odin but kept getting FAILs and Freezes. With this step we lost even the crippled operating system and couldn't reach anything except the 'phone --!-- computer' screen. Luckily, this acts the same as download mode, so not bricked. We kept trying to push the stock SGS4G stock ROM (Froyo 2.2) several times and failing.
At one point we got a completely black screen, wouldn't turn on. Bricked again. We found this post on RootzWiki and it worked for us that time and brought it back from the black screen to download mode http://rootzwiki.com/topic/1820-how-to-unbrick-your-sgs4g/
Somehow we ended up at this guide here on XDA for fixing the "null/null" IMEI http://forum.xda-developers.com/showthread.php?t=1142829
We followed that guide. When you add the PIT file it automatically checks 'Re-Partition' in Odin, we didn't uncheck it. Bricked again. It was stuck on the Samsung logo and when we tried to get to download mode it got stuck on a black screen with the loading circle/lines and 2 computers were giving 'The USB device has malfunctioned' when we plugged it in. The unbrick guide above (RootzWiki) didn't help this time. We tried restarting the computer, let the phone rest without battery for half an hour, held power button for a minute without battery, still nothing.
Finally I accidentally pressed the power button (rather than the volume buttons to get into download mode) and it went to the samsung logo (as expected) and after that I was able to get into download mode. The key to this I think is to keep on trying powering on normally then try download mode over and over and eventually it should get unstuck and the computer should recognize it again.
Once I had it back in download mode, I followed this guide again BUT!!! I made sure to un-check re-partition and I did not check "Phone EFS Clear" (because I had tried that already before it was bricked and wanted to see if a straight ROM would work first). Everything worked perfectly, I got my IMEI and Baseband back, without modifying anything.
I don't know if this was a miracle, or if any of it will work for anyone else, but the moral of the story is don't give up even if you've done the absolute worst possible thing. I don't even think hardbrick exists on this phone after everything we were able to save it from.
Cheers
Click to expand...
Click to collapse
Wheooooooooowwww,..you just UNBRICKED mine, I know of the Battery pull etc...but the post you referenced
is MAGIC
This was not my first Rom nor Root on this phone, it weirdly happened while doing the GB starter....via ODIN, which i also used before..no clue what went wrong, oh well...
Thank you, thank you "i did"....Yohoooo
Yup i agree i like to read, reread then read as i do. This way i got a pretty good understanding of what I'm doing. Btw i have just started using one click and it is sooooo simple. I love it.
Sent from my SGH-T959V using XDA App
The link for fixing null/null IMEI is not working.
http://forum.xda-developers.com/showthread.php?t=1142829
diavel said:
The link for fixing null/null IMEI is not working.
http://forum.xda-developers.com/showthread.php?t=1142829
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=881162
Im still carrying this phone, stupid baseband unlock for iphone won't come out now I am carrying 2 phones, one as an ipod touch and the galaxy s! Good story, hope it can help others, but I am prepared to jump off of this bandwagon anytime now!
Ok so this is my first time posting on XDA so please don't be dicks.
I've been on XDA before and I use it all the time when i've rooted stuff and messed around with my phones. I successfully rooted a GS3 last year and it was awesome and this year i have an LG G2 (ATT version D800). I rooted it a few months back and it took me a little while to do it but it worked. I didn't flash any custom roms or anything but i did use Xposed all the time and it was awesome.
Yesterday like a dumbass i took an OTA update and it put my phone into a bootloop with the message:
ERROR: Boot certification verify
Secure booting error!
Cause: Boot certification verify
Now all my phone does is light up with the LG symbol, flash that message, turn off and keep repeating. I have no download mode, I have no recovery, there is nothing I can do with any variations of button holdings and presses. I can turn it off but I have to hold the power button down for like a solid 15+ seconds to get it to stop. I was running stock firmware from LG, never flashed a single custom ROM on this phone (but I am familiar with it since i use to do it with my GS3 all the time).
Idk what to do, i've been all over the internet and XDA trying to fix this and figure it out. The major problem that I have is that I have a macbook and I know everyone uses PC so not everything from XDA applies to me unfortunately. I don't have access to a PC either unfortunately bc otherwise I would just try fixing it with a PC.
I do have ADB and I have just a little knowledge with that but nothing to extensive.
Please please please help me out, i've never posted anything on a forum before so I hope you guys can help.
PS, I did go to the thread http://forum.xda-developers.com/showthread.php?t=2582142 and that looks great but idk anything about Ubuntu and that whole thing seemed foreign to me unfortunately.
Hello Everybody!
I would like to kindly ask you for some help regarding my Samsung Galaxy Ace Plus S7500 phone. The phone has been locked in a network and further more, in the last months has experienced the autorestart issue. I have read other threads here (before posting this one) and I have seen that other people experience the phone vibrating and continuing to restart in the first two screens. Also, if battery had been taken out, when putting it back in the phone would restart.
After reading the possible solutions here, I have hoped that installing a new ROM on the phone might solve this problem. I have also installed the CWM-based recovery and I believe I have managed to root it. (I am not an expert, but I have managed to root before two Samsung phones after the instructions given here - everything worked flawlessly).
However, yesterday, after obtaining a successful install screen from the version Inspiration_Rom_V18_Kitkat_Edition.zip downloade from this forum, I am stuck with my phone in the CWM-based Recovery v.5.0.2.8 screen. I have tried to install other ROM stable versions from the forum but I seem not to be able to get rid of this screen.
Might I want to add that the phone escaped the former rebooting issue, the battery and the power button seem to work fine now. For example I can shut the phone down, I can restart it, if I take the battery out and put it back in, it will not automatically start. Is there still hope? Have i bricked it?
Please advise and excuse me if I have written anything stupid,
Vlad
[email protected]
mingul said:
Hello Everybody!
I would like to kindly ask you for some help regarding my Samsung Galaxy Ace Plus S7500 phone. The phone has been locked in a network and further more, in the last months has experienced the autorestart issue. I have read other threads here (before posting this one) and I have seen that other people experience the phone vibrating and continuing to restart in the first two screens. Also, if battery had been taken out, when putting it back in the phone would restart.
After reading the possible solutions here, I have hoped that installing a new ROM on the phone might solve this problem. I have also installed the CWM-based recovery and I believe I have managed to root it. (I am not an expert, but I have managed to root before two Samsung phones after the instructions given here - everything worked flawlessly).
However, yesterday, after obtaining a successful install screen from the version Inspiration_Rom_V18_Kitkat_Edition.zip downloade from this forum, I am stuck with my phone in the CWM-based Recovery v.5.0.2.8 screen. I have tried to install other ROM stable versions from the forum but I seem not to be able to get rid of this screen.
Might I want to add that the phone escaped the former rebooting issue, the battery and the power button seem to work fine now. For example I can shut the phone down, I can restart it, if I take the battery out and put it back in, it will not automatically start. Is there still hope? Have i bricked it?
Please advise and excuse me if I have written anything stupid,
Vlad
[email protected]
Click to expand...
Click to collapse
Flash CWM again using ODIN or Flash TWRP (http://forum.xda-developers.com/galaxy-ace-plus/development/twrp-2-7-00-recommended-recovery-cm11-t3073271)
or
Flash Stock ROM
Success!
kk9999gada said:
Flash CWM again using ODIN or Flash TWRP (http://forum.xda-developers.com/galaxy-ace-plus/development/twrp-2-7-00-recommended-recovery-cm11-t3073271)
or
Flash Stock ROM
Click to expand...
Click to collapse
Thanks so much! Succeeded! I have access to my phone again and it is rooted.
However, I did not get rid of the VODAFONE ROMANIAN NETWORK LOCK.
Can I also do this at home?
So here is a string of steps I've already been through in trying to save my bricked Nexus 6: [Can't post outside link yet...]
Basically I got the 'your phone is corrupt' message from google and it kept forcibly shutting down. It would not boot up so someone suggested I side load a rescue OTA. At this point recovery existed and I went through all the steps and had it installing, only to fail mid-way through (~52%) and give me a 'read error' on my command prompt. I started the whole process over again just fine and it got to 73% before 'read error' failing again. I thought no big deal, I'll just keep doing this until it gets to 100%. Nope, recovery is gone. I cannot get there anymore. I start into Fastboot mode and scroll to recovery and hit power and it just goes to a new Fastboot screen and keeps flashing every time I try to select it. The Bootloader logs give me a 'failed to validate boot image: ret=-1' message and says 'Boot up failed.'
I can't find a single guide online that doesn't require recovery mode to work. At this point I don't care about my data and just want to get this phone working again before I throw in the towel and pay Motorola $175 for a refurb. I'm just barely over a year too. The Nexus 'expert' gave up and blamed the memory and maybe he is right but I wanted to run this by you guys first. This phone was completely stock and unrooted.
The only reason why I feel there is still a chance is because when I connect USB my computer reads it as an Android Device in Device Manager with 'Android Bootloader Interface' as a sub device. If the computer can read it, isn't there a chance that some kind of software exists that can forcibly load a new bootloader onto this phone without recovery? I'm 'competent' with computers and android phones but I haven't rooted or done any custom stuff in years so I'm at a loss for what's out there.
Thanks in advance for any help you can give me, even if it's to tell me I'm SOL.
Ok so far I have tried to load a custom recovery but that requires an unlocked bootloader. Then I tried using a toolkit to flash stock as a soft-bricked device but that also requires an unlocked bootloader and I can't unlock the damn bootloader. You know, I thought I was just playing it safe by leaving this phone as-is instead of playing around with it but it looks like I screwed myself by doing so.
Is this the wrong forum for this question?
JQ3 said:
Is this the wrong forum for this question?
Click to expand...
Click to collapse
Sorry for the delay
We have a dedicated help section for your device here
http://forum.xda-developers.com/nexus-6/help
Ask there to receive help
Good luck