Related
Here it goes,
My phone had everything working including 3-button combo.
I successfully upgraded to Gingerbread about a week back and tried Mikey's rom and Icezar's rom.
Last time I was running Continum5.2, decided to downgrade to cognition 4.3.2, without any apparent reason.
Since some one said that you can run Froyo ROm with Gingerbread bootloaders, I decided to keep Gingerbread bootloaders.
Returned to stock JF5 using Icezar's safe method. (The one that does not modifies any boot loaders). Successfully booted to stock and then rebooted to recovery using vol up and power.
Installed Clockwork (2.5) using update.zip. (reinstall packages 2-times), and my phone is in clockwork recovery.
Flashed Cognition 4.3.2, flashed successfully.
Reboot the phone. Nothing happens. It's a hard brick. Have tried almost all the methods to go to download mode, but still unsucessful. I don't see anythng on screen, no light nothing.
Where I went wrong?
Can some one guide about jtag method.
bigbyte.me said:
Here it goes,
My phone had everything working including 3-button combo.
I successfully upgraded to Gingerbread about a week back and tried Mikey's rom and Icezar's rom.
Last time I was running Continum5.2, decided to downgrade to cognition 4.3.2, without any apparent reason.
Since some one said that you can run Froyo ROm with Gingerbread bootloaders, I decided to keep Gingerbread bootloaders.
Returned to stock JF5 using Icezar's safe method. (The one that does not modifies any boot loaders). Successfully booted to stock and then rebooted to recovery using vol up and power.
Installed Clockwork (2.5) using update.zip. (reinstall packages 2-times), and my phone is in clockwork recovery.
Flashed Cognition 4.3.2, flashed successfully.
Reboot the phone. Nothing happens. It's a hard brick. Have tried almost all the methods to go to download mode, but still unsucessful. I don't see anythng on screen, no light nothing.
Where I went wrong?
Can some one guide about jtag method.
Click to expand...
Click to collapse
U got a jig?
Sent from my Captivate using XDA Premium
Zig won't help as nothing is helps only in case of Soft brick.
BTW i figured out where I went wrong, The cognition ROM contains seconday bootloader. So when I flashed it I ended up with Gingerbread primary and Froyo secondary bootloader and hence the Brick. I request all the rom dev to mention at the start of their post if their ROm contains bootloaders.
bigbyte.me said:
Flashed Cognition 4.3.2, flashed successfully.
Click to expand...
Click to collapse
^ That's where you went wrong. Cog flashes sbl. You ended up with one bootloader from 2.3, and one bootloader from 2.2.
There are videos of how to unbrick a perma-bricked phone with a riff box jtag unit on youtube. It'll require you to remove the motherboard and blow $150 or so on a riff box, though.
or you send it to someone with the equiptment, like mobiletechvideos.com and not learn about riff/boxing and spend less money... and and and...
or because it doesnt boot and they cant prove you voided your warranty send it back!
So, this could be avoided doing what?
-Going back to GB stock and from there going back to froyo stock (without 3 button fix)?
I don't think moviletech does crappys something about the solder points too close together.
Edit: but could be wrong.
Sent from my GT-I9000 using XDA Premium App
i was in a similar situation, no 3 button nothing worked my phone wouldn't even power on
but the one method that saved me was this,
Remove battery, SIM card, SD card (if present)
Connect USB cable from computer
While holding down up & down volume, re-insert battery
may be this could help you too.
mobile tech does and has been for over a month, and the first few people are free!
i was able to get myself out of a hard brick, (no buttons no nothing working)
by removing the battery
count to 5
put battery back
DO NOT TOUCH ANY BUTTONS!!!! DO NOT!!! DONT !!!
then put in jig
for me if i touched any buttons the jig would not work.
other methods wouldnt work either.
worth a shot.
You are not the first person I have read about that is not aware that cognition overwrites the boot.bin, and bricked because they flashed it after gingerbread.
Sent from my SAMSUNG-SGH-I897
You messed up with the Bootloader.
Atually I always believe Froyo ROMs should not include Sbl.bin
1tontomato said:
You are not the first person I have read about that is not aware that cognition overwrites the boot.bin, and bricked because they flashed it after gingerbread.
Sent from my SAMSUNG-SGH-I897
Click to expand...
Click to collapse
It overwrites the sbl.bin not boot.bin.
DG put it in so people would always have a 3 button fix(which is contained in the secondary bootloader. sbl.bin)
but with the arrival off the new gb bootloaders means flashing this with those will result in a brick. Guaranteed.
studacris said:
It overwrites the sbl.bin not boot.bin.
DG put it in so people would always have a 3 button fix(which is contained in the secondary bootloader. sbl.bin)
but with the arrival off the new gb bootloaders means flashing this with those will result in a brick. Guaranteed.
Click to expand...
Click to collapse
Yea your right it is the sbl.bin. It was a good idea before gingerbread, but I think it's time has passed especially since it's really easy to get past not having a button combo with a jig. A bad combination of bootloaders is a "brick" for sure.
Sent from my SAMSUNG-SGH-I897
amtrakcn said:
You messed up with the Bootloader.
Atually I always believe Froyo ROMs should not include Sbl.bin
Click to expand...
Click to collapse
Actually, Now I believe that all rom's Froyo or ginger should include either both bootloaders or none.
bigbyte.me said:
Actually, Now I believe that all rom's Froyo or ginger should include either both bootloaders or none.
Click to expand...
Click to collapse
I say none. ANYTIME you touch bootloaders there is a chance of hard bricking. If they don't have any, worst case is a "clay" (soft brick)
TRusselo said:
i was able to get myself out of a hard brick, (no buttons no nothing working)
by removing the battery
count to 5
put battery back
DO NOT TOUCH ANY BUTTONS!!!! DO NOT!!! DONT !!!
then put in jig
....
Click to expand...
Click to collapse
Perhaps I;m not out of the woods yet but a wrong action in ODIN had HB'd my Cappy. Your steps got me back to DL mode. Perhaps it is the 5 count. Patience not being my strong pt I had "not waited" until your recommendation.
I was trying from Continuum5.3 to get back to eclair so to carrier unlock when I made an ODIN error. Still need do that but for now I'll just be thankful that it lives, and move only forward..
its the not touching buttons that makes this trick work
if you replace the battery, what is your normal instinct?
try the power button! or try the button methods...
you are the first to confirm my trick!
congrats!
http://forum.xda-developers.com/showthread.php?t=731989
Use this to get back to stock safely!
[STOCK ROM] Odin3 One-Click Downloader and Drivers CAPTIVATE
use the thanks button!
Hmm very interesting...
I thought your trick worked because it was a screw up in the param.lfs not a bootloader brick, guess not.
im surprised too...
aight so ive searched and searched for all kinda different methods. and done all of them. is it possible to have a permanent brick?
heres the story. i had been running cm10 for prolly 4 or 5 months. no problems. i wanted to check out liquid smooth rom. so i flashed it. no problems. had been running it for a month or so then one day at work when i went on break my network was gone. my apn's were deleted. came home inspected some more and my imei was unknown as well as baseband and many others were unknown. i took it back to stock many times using. gtg method. using heimdel. using odin. with different stock files. from different websites. including xda. i have tried just about everything to re do the phone. including going back to cm10. and other known working roms. ive *#*#4636#*#* and manually switched to gsm which wont change when i click it it still says unknown.
i dont belive it is a rom problem. i have been overclocked 1300mhz. what else is out there can i try. \
\
any help will be very appreciated
Have you by chance odined back to stock then reupgraded to JB? If not I can get you the necessary steps to do so...let me know
Sent from my SGH-I997 using xda premium
FauxAffliction said:
Have you by chance odined back to stock then reupgraded to JB? If not I can get you the necessary steps to do so...let me know
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
yea i went to stock and back to cm10. still nothing. buttt now im unable to do any kinda flashes. im on rooted 2.3.6 threw odin. and no matter what i flash it will say somthing on the lines of failed to find file signature or what ever that code is. i tried changing the cwm in different ways still wont get off the what is it 2.5.2 cwm blue. ive basicly gave up. it seems its to far bricked or whatever the case may be
im sorry i need to correct that. i have not been able to flash to any other roms. i didnt go to stock and then cm10, due the the signature deal on cwm. i was thinking of another time i had problems. so no i have no been able to go to jb after the imei has went unknown
Did you flash a custom kernel to get cwm after going back to stock?
andros11 said:
Did you flash a custom kernel to get cwm after going back to stock?
Click to expand...
Click to collapse
im in able to flash anything.....
really? no one can help me?
Are you trying to flash through Odin? Or through CWM?
Sent from my SGH-I997 using xda premium
psal217050 said:
Are you trying to flash through Odin? Or through CWM?
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
dont know how to flash a cwm threw odin. i tried loading a cwm threw rom manager and manually
kritz84 said:
dont know how to flash a cwm threw odin. i tried loading a cwm threw rom manager and manually
Click to expand...
Click to collapse
but im pretty sure the problem isnt with cwm im more interested in why and how to the imei isnt known and how to fix this problem if theres a cure
Download a heimdall one-click or odin back to stock pack. Open either one up and put your phone in download mode:
- turn off and have the usb cable connected to the pc.
- remove and reinsert battery
- hold both volume buttons and connect usb. Phone should now boot into download mode.
Run program and you will be good. Then look for entropy's dd kernel and flash it in download mode to get cwm.
andros11 said:
Download a heimdall one-click or odin back to stock pack. Open either one up and put your phone in download mode:
- turn off and have the usb cable connected to the pc.
- remove and reinsert battery
- hold both volume buttons and connect usb. Phone should now boot into download mode.
Run program and you will be good. Then look for entropy's dd kernel and flash it in download mode to get cwm.
Click to expand...
Click to collapse
i guess u didnt read my first post. ive already done that. ive done many things....
but anyway weirdest thing just happend. i have been using my phone via wifi. so its been on a while without a sim card inside of it.
\
i noticed i had signal bars. i looked at the imei and its was a number. it was a different iemi then what its supposed to be but there was a imei. baseband was still unknown but anyway i shut the phone done and inserted my sim card. btw its a straight talk sim. and restarted it now im back to unknown imei......
ok so im back on cm10. before i was on cm10 its was giving me the imei which wasnt my original imei. i guess cuz i flashed a efs.tar. but anyway i was able to make a phone call. now im flashed on cm10. and no imei no baseband nothin. i tried flashing the efs again with odin and still nothing. when i do the *#*#4636#*#* it still wont let me switch to gsm. and i cant add a apn.
kritz84 said:
ok so im back on cm10. before i was on cm10 its was giving me the imei which wasnt my original imei. i guess cuz i flashed a efs.tar. but anyway i was able to make a phone call. now im flashed on cm10. and no imei no baseband nothin. i tried flashing the efs again with odin and still nothing. when i do the *#*#4636#*#* it still wont let me switch to gsm. and i cant add a apn.
Click to expand...
Click to collapse
odin or heimdall back to stock.
follow andros11's guide on how to flash jb
he spent the time to write the guide; spend the same amount to time to read the guide
Seems IMEI was kidnapped about a month after Liquid
Ironically, I seem to have EXACTLY the same issue that this original poster has. I have been flashing my Infuse for a little over a year now and I Flashed Liquid, I'd say about 3 weeks ago, maybe end of November. Everything has been smooth sailing. About a 2 days ago I started noticing that my network would just drop - for no reason. But at first it came back. Ok, no problem, probably just a glitch. However yesterday morning it happened again and then I was without the use of data for most of the day until around 6pm. It came back but the bars were grey but I was able to make a phone call. Once I made another call it did not go through, I tried to hangup and it just hung there. there was nothing I could do to get it to hang up. Rebooting the phone resulted in no bars at all. Nothing, nada, ziltch. So last night I reflash it a couple times and notice that there was an update to Liquid (2.1 beta). cool. I wipe, flash 2.1b and it is beautiful. EXCEPT for the fact that I have no network. wifi works fine, but no carrier whatsoever. GRRRR. I decided to back every thing up (have done so several times in the past), stock back down to 2.3.6. Barebones and all it all looked great until I hung up the phone... Same thing. So I went all Rambo on the phone, wiped it down to the very last compound. AT&T wouldn't know the wiser if they took it from me. Master Reset, wiped files, data, I think I took an IC out with all of the wiping I did... Result? No IMEI, circle with the slash. Upset, disappointed and dejected I slumped back to XDA (after I went on Craigslist feeling my phone was broke) to see if I missed anything. That was where I found some links about missing IMEI. To make a long story short, I DO have an old copy of EFS thanks to QKSTER, but I have no idea how to restore. I swear I have been on this since 6:30am and just now am I finding these threads. Must have gone through about 50 others... Sigh. BTW, along the way of my flashing experience today, my network came back temporarily, but I have not relied on it because I knew it would leave me. Just don't know how to use Heimdall to restore. To make a long story short, using Windows, could someone please help me with how to restore my EFS to see if this would solve my dilemma?
808
Dnice808 said:
To make a long story short, I DO have an old copy of EFS thanks to QKSTER, but I have no idea how to restore. I swear I have been on this since 6:30am and just now am I finding these threads. Must have gone through about 50 others... Sigh. BTW, along the way of my flashing experience today, my network came back temporarily, but I have not relied on it because I knew it would leave me. Just don't know how to use Heimdall to restore. To make a long story short, using Windows, could someone please help me with how to restore my EFS to see if this would solve my dilemma?
808
Click to expand...
Click to collapse
What is the format of your EFS folder?
*.zip
*.tar
just a folder?
If you have lost the signal while on JB, see if you can factory reset the phone.
/settings/privacy -reset
Then put it into download mode.
Use the heimdall 1 click uclb3 and flash it once, then without closing heimdall, check the bootloader box and flash it again.
After this, check your imei and band. If it works, no further back up is needed.
If you're still missing the imei, you can flash one of the gb kernel in the second post to get cwm.
Then use the root pack in post #2,
http://forum.xda-developers.com/showthread.php?t=1629079 to install root and su.
install a root tool like root explorer (remember to toggle the r/o r/w) or adb and copy the /efs into the phone's root efs folder,
reboot
check the baseband.
you can also check this thread
http://forum.xda-developers.com/showthread.php?t=1895500
qkster said:
What is the format of your EFS folder?
*.zip
*.tar
just a folder?
So it is in the .tar format that your script backed it up in. Finding another link on the we (which he also linked back to XDA, http://forum.xda-developers.com/showthread.php?t=1264021 I was able to take my backup (that I used with your script) and follow his steps -mostly- (my/your backup had a 'root' folder that had the nv_data.bin file in the afs/settings folder while the instructions did not mention that. I followed the backup location settings (which in turn was also the same as the default that I had backed up)) and replace the EFS folder. It still did not restore it in any flash image just like that. Still had the the circle w/slash. However while I was still searching and typing out that loooong last passage I wrote, my phone network came back for a little while. I know this because I began receiving a bunch of texts. I was able to make a phone call. But it still happened again when I made another, it did not go through and when I hung up, it just stayed there looking at me with its grey, blank look. Even killing the phone app did not work. I rebooted back to the same drama.
If you have lost the signal while on JB, see if you can factory reset the phone.
/settings/privacy -reset
I actually was on 2.3.6 using your posts, first the basic rooted flash having to then using the Entropy kernel and then I did the lazy flash that was already rooted and just having to add the vold file to /system/etc/blah/blah. I do want to add that I DID have wifi active at this time and it may not be associated, but the first poster did mention he felt it may have had something to do with it. With wifi on, after awhile of me NOT looking at the phohe (actually doing so made me want to HULK SMASH), the network came on and my texts came in. I was able to look in settings and see ATT, and my IMEI. I was almost finished with my passage to you so I decided to update to Liquid 2.1 beta, but moving up to JB, then to LiquidSmooth. Of course doing so I got the circle w/slash, but wifi started restoring my apps.
Earlier I mentioned that I did a whole rubba dub dub, meaning I did do the /settings/privacy -reset thingy, wiping the phones carcass. I will do it again (at this point nothing to lose), following everything you ask to a 'T'.
808
Click to expand...
Click to collapse
qkster said:
What is the format of your EFS folder?
*.zip
*.tar
just a folder?
If you have lost the signal while on JB, see if you can factory reset the phone.
/settings/privacy -reset
Then put it into download mode.
Done.
Use the heimdall 1 click uclb3 and flash it once, then without closing heimdall, check the bootloader box and flash it again.
Done
After this, check your imei and band. If it works, no further back up is needed.
Sigh, did not do a darn thing. Circle w/slash.
If you're still missing the imei, you can flash one of the gb kernel in the second post to get cwm.
Done.
Then use the root pack in post #2,
http://forum.xda-developers.com/showthread.php?t=1629079 to install root and su.
install a root tool like root explorer (remember to toggle the r/o r/w) or adb and copy the /efs into the phone's root efs folder,
reboot
check the baseband.
Went in Root Explorer, did the toggle, deleted the contents of efs then copied the contents of my backup into there. Rebooted. Nada.
you can also check this thread
http://forum.xda-developers.com/showthread.php?t=1895500
I then was going to try the other link using Odin, but I cannot get Odin to see my phone. I read some thread talking about if I use Heimdall I will have problems using Odin because they use the same ports? How frustrating. The weird part is now that I have the flashed, rooted 2.3.6 image and using wifi, at some point tonight my network may come back on. Or it may not.
808
Click to expand...
Click to collapse
Bugged out, huh?!!???
Dnice808 said:
Bugged out, huh?!!???
Click to expand...
Click to collapse
I wasn't sure if there was a question there.
From my experience, flashing to JB (MTD partition) from GB without going through ICS may result in lost of imei.
Sometimes, it just happens. I had very limited experience with JB.
The few methods that I've tried worked for me. Just simply flashing back to stock with a re-partition ( (Heimdall -1-click for me) usually brings back the /efs and imei without doing anything extra.
If you haven't, and if you can, I would try the heimdall-1-click a few times.
If you want to use Odin, you may need to reinstall samsung drivers and use a different usb port on the PC than the one you used for heimdall.
You may also want to check the signal of the phone at your location. you may be getting poor signal and it has nothing to do with the phone's OS
qkster said:
I wasn't sure if there was a question there.
Click to expand...
Click to collapse
Me stating that it is bugged out, was me just confirming that it is Weird!
qkster said:
From my experience, flashing to JB (MTD partition) from GB without going through ICS may result in lost of imei.
Sometimes, it just happens. I had very limited experience with JB.
Click to expand...
Click to collapse
Ok just to explain myself better. I have been saying that I was going from GB to JB when in fact I meant to say that I was going from GB to ICS. Sorry for that. Also, the reason my responses have looked wacky is that I was trying to select the multi quote button and getting no response. Hopefully this response is a little more organized.
qkster said:
The few methods that I've tried worked for me. Just simply flashing back to stock with a re-partition ( (Heimdall -1-click for me) usually brings back the /efs and imei without doing anything extra.
If you haven't, and if you can, I would try the heimdall-1-click a few times.
Click to expand...
Click to collapse
See that is what confuses me too. I have flashed back and forth several times at this point, and sometimes the /efs and imei do come back, but now they have never stayed. It is the only reason why I have tried to pretty much rule out a hardware issue. Even when I flash and there is no imei, there is the same /efs folder. And when I wipe the whole thing sparkling clean, even the newly formed /efs folder has the correct imei but it is just not being recognized on the phone.
qkster said:
If you want to use Odin, you may need to reinstall samsung drivers and use a different usb port on the PC than the one you used for heimdall.
Click to expand...
Click to collapse
Of course what I did was accidentally leave my phone home preventing me from testing it out with Odin on another machine. Its all good though.
qkster said:
You may also want to check the signal of the phone at your location. you may be getting poor signal and it has nothing to do with the phone's OS
Click to expand...
Click to collapse
I have an AT&T prepaid phone and the sim from the Infuse works in it flawlessly...
808
Before you post, "BLAKDSKF READ OTHER FORUMS BLUSDFLU!!!!!!!111!!!", please, PLEASE, read the whole post. I am not illiterate or a fool. I've spent the last few days researching similar posts, both on xda and other sites, and as far as I've found, this is the only post of this kind on the Verizon SGSIII forums, though there are some that are somewhat similar in the other SGSIII forums (though I think the root of the problem is different). If you can prove me wrong, please redirect.
The Long Story:
ok. SO. I was trying to root my SGSIII, unlock the bootloader, and install CM10. Simple enough, right? Not so. I got through the rooting tutorial at Link 1 relatively smoothly. For the record, I did the composite root and bootloader combo, and I installed CWM Touch Recovery, as per the guide. I also restored the Jellybean Bootchain. I think it was at this point I downloaded Titanium Backup (because forethought is not my forte) and backed up all my apps. I also made a backup with CWM Recovery, but there were errors. I forget the reason, but it aborted backup. I then tried to make a backup onto my external sd card, and some other errors popped up. Mainly that it couldn't find /android.secure (something along those lines) or /sd-ext (might have been something else. I'm going off memory) and skipped them. It still made the backup, so my illiterate, foolish self decided to roll with it and go ahead.
I then went ahead to Link 2, and with it being 2 AM, I stupidly decided to screw trying to figure out how to use Heimdall 1.4rc1 and continue to use ODIN for flashing. After all what's the difference, I thought. One flashing program is the same as another. I flashed the first two files. Well, in truth, I'm not sure if I flashed the first file. Since I just made a single folder for all the SGSIII Verizon flashing stuff, I had two files with similar names at the time. One from Link 1 and one from Link 2. The only difference was one was a boot chain, the other was a boot loader. Also, one ended with .md5 while the other ended with .tar. Sadly I tiredly picked one and flashed it. I think it was the .md5 one, but I'm not sure. Around this point, my micro sd card reader broke, so I decided to just use my other phone (Motorola Photon 4g running Joker's CM9) as a reader of sorts. I swapped them, used my phone to put the zip from Link 2 on it, and swapped them back. I say this because I'm not sure if that is what broke my md5sums or not (more on that in a sec).
Well, surprise, surprise, my phone got stuck on the animated, colorful "4G LTE" boot screen, except it was fully black, though the noise was playing. I think to myself, "No biggie. I'll just restore my previous backup," so I go back to restore it when I get the error 'md5sum mismatch'. I look up the problem, and after extensive, 3AM research (read: clicked the first link on google and blindly followed), I went with one guys advice, which was to create a blank nandroid.md5 file to force the restore. I figured, "Hey. This is pretty risky. I think I'll just restore the bootloader instead of the whole restore." Or at least that's what was going through my head as I went through with restoring the whole backup. Lo and behold, /system was corrupted, I assume, and it aborted restoring it. I reboot my phone only to find out that my phone gets stuck on the SGSIII boot logo. This is where I am now. I would go through with flashing a stock rom onto it to undo everything I've done, but ODIN won't recognize my phone anymore. I can still get into Download and Recovery Mode. All my backups are useless at the moment.
In Short:
I tried to root, unlock the bootloader, and flash CM10 on it
I messed up and ended up restoring a broken backup, md5sums be screwed.
Now ODIN won't recognize my phone and it's stuck at the SGSIII boot screen.
Is there any way to fix this or at least return it back to stock so I can start again?
If there's any other information you need, just ask. I'd be happy to give it. :laugh: This is my first post on these forums, so I'm not sure what information is standard. If you have any idea of what it might be, please drop a comment or something rather than just leaving. I'd like to know that people are actually reading this post.
And on an unrelated note, every time I try to flash with Heimdall, I get an error about there not being a certain .dll file, even though I downloaded the package from Link 2. Am I doing something wrong?
EDIT: I've already tried factory resetting and wiping the cache/dalvik cache. Most of my info is backed up anyway.
Links:
Link 1: http://forum.xda-developers.com/showthread.php?t=2046439
Link 2: http://wiki.cyanogenmod.org/w/Install_CM_for_d2vzw
What happens when you plug your phone into your PC? Have you tried deleting the drivers then reinstalling them either from Samsung or from the Kies program? You really have to try to mess up this phone and it seems like you definitely tried very hard in this regard.
Edit: Idk anything about Heimdall, I use Odin only so I can't help you there.
SlimSnoopOS said:
What happens when you plug your phone into your PC? Have you tried deleting the drivers then reinstalling them either from Samsung or from the Kies program? You really have to try to mess up this phone and it seems like you definitely tried very hard in this regard.
Edit: Idk anything about Heimdall, I use Odin only so I can't help you there.
Click to expand...
Click to collapse
I hadn't noticed before, but my phone doesn't even show a charge screen when plugged in, but that might just be the settings on the phone pre-root. I'm not sure because I left the phone on to see if it was just a time thing. The phone died and I have to recharge it.
After goofing around with the phone while on the charger for a while, I can get a charge screen to show up for a second. The standard "battery with a loading circle" type symbol for this type of error.
I just reinstalled the drivers. I'll let the phone charge for about 10 minutes or so, then test the phone.
dudeman9199 said:
I hadn't noticed before, but my phone doesn't even show a charge screen when plugged in, but that might just be the settings on the phone pre-root. I'm not sure because I left the phone on to see if it was just a time thing. The phone died and I have to recharge it.
After goofing around with the phone while on the charger for a while, I can get a charge screen to show up for a second. The standard "battery with a loading circle" type symbol for this type of error.
I just reinstalled the drivers. I'll let the phone charge for about 10 minutes or so, then test the phone.
Click to expand...
Click to collapse
Well if it died you should leave it on the charger longer than ten minutes if it is charging. If Odin recognizes it, your first step would be to try flashing a stock image.
SlimSnoopOS said:
Well if it died you should leave it on the charger longer than ten minutes if it is charging. If Odin recognizes it, your first step would be to try flashing a stock image.
Click to expand...
Click to collapse
Thanks. It would seem that it now recognizes the phone, from what I can tell. As soon as I get a stock rom, I'll flash it and post an update.
dudeman9199 said:
Thanks. It would seem that it now recognizes the phone, from what I can tell. As soon as I get a stock rom, I'll flash it and post an update.
Click to expand...
Click to collapse
Great! Use Droidstyle's guide or MrRobinson's thread for the proper images. Should be a good starting point.
Sent from my SCH-I535 using xda app-developers app
I just wanted to add that THIS is how you do a first post or any help needed post! Great details and is obvious you researchedyour problem as well.
The errors in cwm are actually normal. I think the corrupt backups are unrelated.
Sent from my SCH-I605 (AKA NOTE 2)
SlimSnoopOS said:
Great! Use Droidstyle's guide or MrRobinson's thread for the proper images. Should be a good starting point.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I've finally booted up into the setup wizard. I guess from here on I can re-root, unlock the bootloader, and *hopefully* get a working backup and eventually flash CM10.
I guess this means Problem Solved? Again, Thanks.
kintwofan said:
I just wanted to add that THIS is how you do a first post or any help needed post! Great details and is obvious you researchedyour problem as well.
The errors in cwm are actually normal. I think the corrupt backups are unrelated.
Sent from my SCH-I605 (AKA NOTE 2)
Click to expand...
Click to collapse
Thanks. I'm just gonna assume that the problems stemmed from swapping the sd card and leave it at that.
dudeman9199 said:
Thanks. I've finally booted up into the setup wizard. I guess from here on I can re-root, unlock the bootloader, and *hopefully* get a working backup and eventually flash CM10.
I guess this means Problem Solved? Again, Thanks.
Thanks. I'm just gonna assume that the problems stemmed from swapping the sd card and leave it at that.
Click to expand...
Click to collapse
Perfect! Which thread did you end up using btw?
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Perfect! Which thread did you end up using btw?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I used droidstyle's thread for getting the stock rom.
Ok, yesterday morning my MAXX received the KitKat update. Brainlessly, I clicked upgrade. This put me into the oh so famous bootloop.
During one of the boot loops, I managed to unroot with Voodoo.
Then in fastboot, I had the brilliant (aka, incredibly stupid) idea of flashing an old recovery. I had thought it was the one from 4.2.2 but sadly, it was from the previous version.
This had the appearance of working as it then booted to KitKat upgrade, which after a couple minutes failed.
Now I'm completely stuck in fastboot mode. I can't flash the 4.2.2 recovery. I haven't tried anything else. FXZ back to 12.15.15 doesn't work. Gives the GPT failure.
So...my belief, based only on googling around, is that I need to wait for the FXZ for KitKat. Does that sound right?
Any other ideas?
Thank you in advance!!!!!!!!!!
killboredom said:
Ok, yesterday morning my MAXX received the KitKat update. Brainlessly, I clicked upgrade. This put me into the oh so famous bootloop.
During one of the boot loops, I managed to unroot with Voodoo.
Then in fastboot, I had the brilliant (aka, incredibly stupid) idea of flashing an old recovery. I had thought it was the one from 4.2.2 but sadly, it was from the previous version.
This had the appearance of working as it then booted to KitKat upgrade, which after a couple minutes failed.
Now I'm completely stuck in fastboot mode. I can't flash the 4.2.2 recovery. I haven't tried anything else. FXZ back to 12.15.15 doesn't work. Gives the GPT failure.
So...my belief, based only on googling around, is that I need to wait for the FXZ for KitKat. Does that sound right?
Any other ideas?
Thank you in advance!!!!!!!!!!
Click to expand...
Click to collapse
I think that's right. It's ridiculous that by locking things down and preventing us from unlocking bootloader Verizon actually causes bricks of this nature to occur. If you had an unlocked bootloader you'd be 100% fine right now.
Sent from my Nexus 7
There is a way. I posted in previous forum.
Use fastboot
Fastboot wipe cache
Fastboot wipe user data
Try this if not pm me and I will help you out one on one
That should fix your issue
Sent from my XT1080 using xda app-developers app
phositadc said:
I think that's right. It's ridiculous that by locking things down and preventing us from unlocking bootloader Verizon actually causes bricks of this nature to occur. If you had an unlocked bootloader you'd be 100% fine right now.
Sent from my Nexus 7
Click to expand...
Click to collapse
If he hadn't brute forced a root method and messed with his phone he'd be 100% fine too
codito said:
If he hadn't brute forced a root method and messed with his phone he'd be 100% fine too
Click to expand...
Click to collapse
Ha...well there is that But what fun would that be?
The sad part is that the manufacturers could care less about giving us an unlocked bootloader. Android is a great ecosystem to play with and learn with and improve with. It's the carriers that are so paranoid about taking any tiny dent in their enormous profits that want to keep us locked out. So shame on them.
But, to be fair, I know the risks of the world we live in and this is my first brick in four Android phones, so I'm fine with it.
codito said:
If he hadn't brute forced a root method and messed with his phone he'd be 100% fine too
Click to expand...
Click to collapse
My point was merely that it's somewhat ironic that, by trying to prevent bricks by locking bootloaders, Verizon actually causes some bricks that would be avoided with an unlocked bootloader.
Not saying anything about whether what he was doing is right or wrong, or whether Verizon prevents more bricks than it causes.
Sent from my Nexus 7
Edit: but you've got to wonder. Are you more likely to brick using one of these crazy complicated methods we have to use to get around Verizon security? Or using fastboot OEM unlock + flash superuser. I bet per hundred rooted phones, less Nexus's (and other unlockable phones) are bricked than phones that are tightly locked down. Pure speculation of course.
killboredom said:
Ok, yesterday morning my MAXX received the KitKat update. Brainlessly, I clicked upgrade. This put me into the oh so famous bootloop.
During one of the boot loops, I managed to unroot with Voodoo.
Then in fastboot, I had the brilliant (aka, incredibly stupid) idea of flashing an old recovery. I had thought it was the one from 4.2.2 but sadly, it was from the previous version.
This had the appearance of working as it then booted to KitKat upgrade, which after a couple minutes failed.
Now I'm completely stuck in fastboot mode. I can't flash the 4.2.2 recovery. I haven't tried anything else. FXZ back to 12.15.15 doesn't work. Gives the GPT failure.
So...my belief, based only on googling around, is that I need to wait for the FXZ for KitKat. Does that sound right?
Any other ideas?
Thank you in advance!!!!!!!!!!
Click to expand...
Click to collapse
It sounds like you're actually stuck partially on JB, partially on KK, hence why you're bootlooping. I had a very similar issue when I tried to install the KK update through update.zip .......... after a couple hours, I finally got it back up and running.
My method - use the Method 2 Manual flash steps I posted in Dev section here - http://forum.xda-developers.com/showthread.php?t=2580060
Let me know if it works. I had problems at first, but that should cover it. Getting system to flash was actually the hardest part
So I've been waiting on a unified firmware before trying CM. Don't judge me. However, I can't get it to boot. CWM recovery works fine, wiping /data and /cache works fine, as does installing the zip.
I tried both nightlies, and both won't boot beyond the Moto 'BOOTLOADER UNLOCKED" warning. This is the Verizon RAZR HD.
Any thoughts?
same for me
I got the exact same behavior. I think todays nightly should be sorted out.
Ask in QA
Saludos
gustrick said:
Ask in QA
Saludos
Click to expand...
Click to collapse
I finally got it worked out. I have a feeling my recovery image may have been corrupted. It installed fine, but you never know.
Either way, these are the files I used (for others to reference)
recovery-clockwork-6.0.4.4-xt926
d688093be16b953f860b35341df3ab08
cm-11-20140220-NIGHTLY-moto_msm8960
847519fbff300dc35538bf61785065be
-- Also, don't forget to format /system. You'll have to dig for that option in the storage and mounts section of your recovery
SCFirefighter said:
I finally got it worked out. I have a feeling my recovery image may have been corrupted. It installed fine, but you never know.
Either way, these are the files I used (for others to reference)
recovery-clockwork-6.0.4.4-xt926
d688093be16b953f860b35341df3ab08
cm-11-20140220-NIGHTLY-moto_msm8960
847519fbff300dc35538bf61785065be
-- Also, don't forget to format /system. You'll have to dig for that option in the mounds section of your recovery
Click to expand...
Click to collapse
Use philz 6128 w/cwmr 6047.
I'm having a weird issue with the latest unified build, I get stuck on "warning bootloader unlocked" but only when I power off the phone to charge it lol
Sent from my RAZR HD
What is the difference between moto_msm8960 and moto_msm8960dt?
Sent from my Droid Razr Maxx HD
XBlackChaosX said:
What is the difference between moto_msm8960 and moto_msm8960dt?
Sent from my Droid Razr Maxx HD
Click to expand...
Click to collapse
The dt is for the Moto X I believe.
Sent from my DROID RAZR HD using Tapatalk
I can't see, to be able to get this rom to detect my T-Mobile Sim.
Sent from my Droid Razr Maxx HD
Hydr0id said:
I'm having a weird issue with the latest unified build, I get stuck on "warning bootloader unlocked" but only when I power off the phone to charge it lol
Sent from my RAZR HD
Click to expand...
Click to collapse
I have the same problem on unified from Feb21st. I'm afraid that when my battery goes, I'll have a soft-bricked phone because it won't charge.
When installing CM, one thing I did not do was formatting /system, because I couldn't find that option anywhere on CWM.
Does anyone know a way to fix this?
MauricioBR said:
I have the same problem on unified from Feb21st. I'm afraid that when my battery goes, I'll have a soft-bricked phone because it won't charge.
When installing CM, one thing I did not do was formatting /system, because I couldn't find that option anywhere on CWM.
Does anyone know a way to fix this?
Click to expand...
Click to collapse
I thought I was the only one, I can confirm the problem still persists on 2/24 nightly, on today's one I haven't tried yet. Also, the format/system is under mounts & storage in the main menu of CWM. I did a clean install of the unified nightlies, that hasn't solved my problem, I'm really concerned of what could happen if my phone powers off and there is no way to past the "bootloader unlocked" screen.
Sent from my RAZR HD using Tapatalk
While I certainly hope you guys can get back on your feet I would advise you to get the team black hat active USB connector. It allows your phone to boot and flash without battery.
eta: http://shop.teamblackhat.info/Factory-style-programming-cable-for-Motorola-FactCable.htm
I have no ties to these folks or this product, except for owning one. It has saved twice in 2 years. Don't need it much, but you'll be glad to have it when you need it.
It took me over 8 hours of on and off flashing before I got it right. I blamed it on my recovery, since the md5's of all the zips I downloaded were correct, even after copying them to the sd card via my laptop.
I would try this:
Find your original Motorola usb cable. I've seen a lot of posts over the years because of bad cables.
Make sure you have the right one, and re-flash CWM recovery. Check its md5 before flashing using the one from my earlier post.
Boot into CWM and format /data and /cache, and then find the option to format /system.
Flash the nighly from http://get.cm/?device=moto_msm8960
Flash the gapps package for CM11: http://wiki.cyanogenmod.org/w/Google_Apps
Reboot
Even if you've done this already, just try it again. Like I said I spent all day getting frustrated, and almost gave up on it. I am not entirely sure it was my recovery, but I have nothing else to blame it on.
Good luck.
SCFirefighter said:
While I certainly hope you guys can get back on your feet I would advise you to get the team black hat active USB connector. It allows your phone to boot and flash without battery.
[...]
I have no ties to these folks or this product, except for owning one. It has saved twice in 2 years. Don't need it much, but you'll be glad to have it when you need it.
It took me over 8 hours of on and off flashing before I got it right. I blamed it on my recovery, since the md5's of all the zips I downloaded were correct, even after copying them to the sd card via my laptop.
I would try this:
[...]
Even if you've done this already, just try it again. Like I said I spent all day getting frustrated, and almost gave up on it. I am not entirely sure it was my recovery, but I have nothing else to blame it on.
Good luck.
Click to expand...
Click to collapse
I just installed the last non-unified version and it's working as expected. I'll use this version for now, until the problem is fixed.
Are you using the official CWM? And which fastboot utility do you recommend? I know that the one that comes from SDK can cause issues with moto.
MauricioBR said:
I just installed the last non-unified version and it's working as expected. I'll use this version for now, until the problem is fixed.
Are you using the official CWM? And which fastboot utility do you recommend? I know that the one that comes from SDK can cause issues with moto.
Click to expand...
Click to collapse
Congrats! Try doing the OTA updates to the unified builds. I've read that is successful. I used snapdragon specific fastboots I found online a while ago. However, I've never really seen it specified, so I assume the normal one that come with the SDK will work just fine.
SCFirefighter said:
Congrats! Try doing the OTA updates to the unified builds. I've read that is successful. I used snapdragon specific fastboots I found online a while ago. However, I've never really seen it specified, so I assume the normal one that come with the SDK will work just fine.
Click to expand...
Click to collapse
The unified versions do not show up on the updater.
I tried to search another way to do the OTA, but had no luck. I tried installing the unified from the 24th over the non-unified (without wipes), but the charging problem came back.
Next step is to try flashing CWM over again and will go from that -- although I find hard to believe that the same CWM that works for one version is causing the other to bug out.
I've pushed and merged the fix for charge only mode: http://review.cyanogenmod.org/60302
It will be fixed in the next nightly.
kabaldan said:
I've pushed and merged the fix for charge only mode: [...]
It will be fixed in the next nightly.
Click to expand...
Click to collapse
Wow, thanks so much!
I saw it was added on the nightly and I'm downloading right now to test it.
Edit: It's fixed! Thanks again!
I can't believe how inconsistent this **** is. So I messed up my phone and wanted to start over. Now the same files I successfully flashed and booted (see first page) now don't boot past the bootloader screen again.
Even after flashing the Verizon stock image back into my phone, the same files that were still on my external sd card refuse to successfully boot.
w t f
ETA: I am so f'n pissed right now. I was so happy with CM and I spent the last hours trying to get this back on my phone. Ready to throw this thing out. 2 different recoveries, 5 different CM zips. NONE boot past the bootloader image!!!!!!!!!!!!!!!!
SCFirefighter said:
I can't believe how inconsistent this **** is. So I messed up my phone and wanted to start over. Now the same files I successfully flashed and booted (see first page) now don't boot past the bootloader screen again.
Even after flashing the Verizon stock image back into my phone, the same files that were still on my external sd card refuse to successfully boot.
w t f
ETA: I am so f'n pissed right now. I was so happy with CM and I spent the last hours trying to get this back on my phone. Ready to throw this thing out. 2 different recoveries, 5 different CM zips. NONE boot past the bootloader image!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
I take it that stock rsd restore was successful for a boot to stock & the 1st boot to google login & getting to homesreen & etc? You are referring to failures after this 1st stock boot right?
Just to be on the same page.
aviwdoowks said:
I take it that stock rsd restore was successful for a boot to stock & the 1st boot to google login & getting to homesreen & etc? You are referring to failures after this 1st stock boot right?
Just to be on the same page.
Click to expand...
Click to collapse
Flashing back to stock results in a fully functional phone. When I boot into the custom recovery and format everything followed by the zips I just don't get it to boot at all.it just hangs at the unlocked boot loader warning.