Related
Dani897 has already made a discussion of this, but I'm moving this information over as an official post in the Infuse 4G section as well.
This is from existz/untermensch's thread. I take no credit. See here for more info http://forum.xda-developers.com/showthread.php?t=909213
Making this modification will allow you to flash un-signed .zip files due to signature verification being turned off. (3e requires root)
* Download and extract the .zip
* Use a terminal emulator or ADB Shell and mount system as read/write.
* For backup purposes, use adb or root explorer to rename the current recovery file in /system/bin to recovery.orig
* Use a file manager (Root Explorer) and copy the new recovery file to /system/bin
* Reboot and your 3e (Froyo stock) recovery will no longer require signature checking.
You can now use this recovery or use the CWM from Captivate (posted in another thread here).
I am not responsible if this bricks your phone. This is easy cheese...just follow these steps.
Download:
3e Recovery w/o signature verification
Youtube video using Root Explorer from gtg465x (Make sure to Thank him!!)
You actually tested this on an Infuse?
DarkH2O said:
You actually tested this on an Infuse?
Click to expand...
Click to collapse
Yes. it is working on mine right now.
i already tested this days ago and cwm
except using truselos super easy batch script to make it even more easy for people to use.
http://forum.xda-developers.com/showthread.php?t=1086622
still there is disbelief. yes people it works! im not sure what trouble people are having flahsing roms but cwm and 3e can flash .zip files just fine. i expected to see some flashable mods and themes by now. i have successfully flashed files for testing purposes and im not too advanced of a user. i planed to post some things like a market fix and such but i have been disrtacted.
Dani897 said:
i already tested this days ago and cwm
except using truselos super easy batch script to make it even more easy for people to use.
http://forum.xda-developers.com/showthread.php?t=1086622
still there is disbelief. yes people it works! im not sure what trouble people are having flahsing roms but cwm and 3e can flash .zip files just fine. i expected to see some flashable mods and themes by now. i have successfully flashed files for testing purposes and im not too advanced of a user. i planed to post some things like a market fix and such but i have been disrtacted.
Click to expand...
Click to collapse
Dani, i completely agree. If you notice, I made mention of your testing at the top of the article.
Now that there is a dedicated thread, its much more likely to be realized that this works FINE. I think once I get a tester for the Odin package I slapped together to get us back to stock in case we brick, and get it successfully setup, i'll put a thread out and we can REALLY get to work on some ROMs.
So far, this phone's software is nearly identical to the Captivate, meaning we will just need to port from the Captivate and we will have a mass of ROMs in no time!
h8rift said:
Dani, i completely agree. If you notice, I made mention of your testing at the top of the article.
Now that there is a dedicated thread, its much more likely to be realized that this works FINE. I think once I get a tester for the Odin package I slapped together to get us back to stock in case we brick, and get it successfully setup, i'll put a thread out and we can REALLY get to work on some ROMs.
So far, this phone's software is nearly identical to the Captivate, meaning we will just need to port from the Captivate and we will have a mass of ROMs in no time!
Click to expand...
Click to collapse
as soon as we get some kernel dev on this thing i agree. porting will be easy. thanks for the write ups too. are you planning to get a second phone? i would test if i had two of them. my captivate will go to my brother, if it weren't for that id have probably bricked it and begged some people to try making new odin packages for me to fix it.
i understand that after a brick the user hates not having the phone and may be very tempted to return it but it is helpful to everyone to try all you can to recover it. if mine bricks im using the insureance plan and saying it was stolen, then i will have a dedicated test phone.
I have an Atrix as well, but would prefer someone who may have already bricked to try this package that i wrote up this morning.
I dont mind someone wanting to swap.their phone...but i literally need about an hour or two of time with the brick's user and its very likely that we will have working Odin....and then you and i...as well as others... can do kernel and rom deving nearly immediately. We have source already, so we only need to test this safety net . PM me if you find someone who is bricked or is willing to test!!
-h8
Dani897 said:
as soon as we get some kernel dev on this thing i agree. porting will be easy. thanks for the write ups too. are you planning to get a second phone? i would test if i had two of them. my captivate will go to my brother, if it weren't for that id have probably bricked it and begged some people to try making new odin packages for me to fix it.
i understand that after a brick the user hates not having the phone and may be very tempted to return it but it is helpful to everyone to try all you can to recover it. if mine bricks im using the insureance plan and saying it was stolen, then i will have a dedicated test phone.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I997 using XDA App
I have a bricked Infuse im not sure what caused the crash. I was running stock rooted by the super one click method and was uninstalling an app when it went all black except the bottom keys. Doesnt do much of anything else now. I attempted an odin fix someone suggested to no avail. I can get into download mode still but nothing else. Id be willing to try anything to unbrick it .
it's working for me, I unzipped, put the file in my dropbox, downloaded the file on phone from dropbox, used root explorer to mount, (I'm already rooted) copied the file, went to system/bin, renamed the original, then pasted the new file, rebooted, flashed CWM to captivate, and rebooted into recovery, and it works. I still have my HTC Inspire, i'm on a 30 day run here to see if i like the infuse. So far it's the best GPS i've had, and i've had a lot of phones. I hate to think I spent 600 bucks on a another captivate. I had that phone as well, but so far i really like it.
Realityfalse said:
I have a bricked Infuse im not sure what caused the crash. I was running stock rooted by the super one click method and was uninstalling an app when it went all black except the bottom keys. Doesnt do much of anything else now. I attempted an odin fix someone suggested to no avail. I can get into download mode still but nothing else. Id be willing to try anything to unbrick it .
Click to expand...
Click to collapse
if you can get into download mode I personally would try running the captivate odin and see what happens, buts that's just me lol. I'm a risk taker lol.
What commands do you use in ADB to mount system as read/write?
budco2000 said:
if you can get into download mode I personally would try running the captivate odin and see what happens, buts that's just me lol. I'm a risk taker lol.
Click to expand...
Click to collapse
dont do that. you dont want the captivate param.ifs on here. you may loose download mode if the boot parameters get messed up. especially dont flash anything with bootloaders, that means no one click nad no 3-button fix roms. this may be similar to the galaxy s but there are atleast a few differences in hardware layout that would make that a bad idea. for instance this can run gps and camera during phone calls. the sgs cant so the way things comunicate on the board may be differet, it may also just be differences in the kernel or framework but we cant be sure.
Dani897 said:
dont do that. you dont want the captivate param.ifs on here. you may loose download mode if the boot parameters get messed up. especially dont flash anything with bootloaders, that means no one click nad no 3-button fix roms. this may be similar to the galaxy s but there are atleast a few differences in hardware layout that would make that a bad idea. for instance this can run gps and camera during phone calls. the sgs cant so the way things comunicate on the board may be differet, it may also just be differences in the kernel or framework but we cant be sure.
Click to expand...
Click to collapse
Yes. DO NOT DO that.
BTW, I just had a successful Odin flash with beatblaster! His framework-res was broken, and he flashed all stock partitions successfully. Hope to be posting it up to the masses in about an hour; After he does some initial checks now that he's back to stock to make sure everything is 100%!
Let's get this party started ....stay tuned!
h8rift said:
Yes. DO NOT DO that.
BTW, I just had a successful Odin flash with beatblaster! His framework-res was broken, and he flashed all stock partitions successfully. Hope to be posting it up to the masses in about an hour; After he does some initial checks now that he's back to stock to make sure everything is 100%!
Let's get this party started ....stay tuned!
Click to expand...
Click to collapse
yaaay
ok now we can get all crazy with few worries. good to hear!
Dani897 said:
yaaay
ok now we can get all crazy with few worries. good to hear!
Click to expand...
Click to collapse
Yes. That's a major hurdle.
h8rift said:
Yes. DO NOT DO that.
BTW, I just had a successful Odin flash with beatblaster! His framework-res was broken, and he flashed all stock partitions successfully. Hope to be posting it up to the masses in about an hour; After he does some initial checks now that he's back to stock to make sure everything is 100%!
Let's get this party started ....stay tuned!
Click to expand...
Click to collapse
Sweet! So the dump was good then it sounds like. So just to sum it all up, odin the pda tar and it restores and wipes EVERYTHING!
Woops! AND DEODEXED!!?!?
I'm pretty new to all of this, but here is how I did it. Make sure you have busybox installed!
Extract the "recovery" file to your phone's internal SD card.
On your phone, go into your terminal emulator.
Type in "su" and press enter.
Type in "cd /sdcard" and press enter.
Type in "mount -o rw,remount /dev/block/stl9 /system"
Type in "cp -f recovery /system/bin" and press enter.
Reboot your phone.
Maybe this will help someone. Maybe it's not even the right way to do this, and my phone will soon explode. I'm a pretty big noob with this, so someone let me know.
PS: If you brick your phone, it isn't my fault.
Hi I came from iPhone 4 and like 2days owning this infuse, I am trying to follow gtg465x to install his ROM, I am done with the rooting and his next step is to "install 3e recovery" now that I am here I am totally lost, I downloaded the file here my Questions are:
1.where do I extract the zip I donwloaded from here? From the SD card root?
2. What thing will I use Terminal emulator or ADB SHELL to make it read/write is that 2 an Android apps I'm lost here. I am trying to be careful, I searched and found too much post and way different doing this. So now I am confuse.
Can anybody tell me how it install 3e recovery the easy and idiot proof way, like I said I am new to android I really have no idea about everything, and most of them too are initial I don't even know what the initials means. Anyone? Thanks
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
spirikitik said:
Hi I came from iPhone 4 and like 2days owning this infuse, I am trying to follow gtg465x to install his ROM, I am done with the rooting and his next step is to "install 3e recovery" now that I am here I am totally lost, I downloaded the file here my Questions are:
1.where do I extract the zip I donwloaded from here? From the SD card root?
2. What thing will I use Terminal emulator or ADB SHELL to make it read/write is that 2 an Android apps I'm lost here. I am trying to be careful, I searched and found too much post and way different doing this. So now I am confuse.
Can anybody tell me how it install 3e recovery the easy and idiot proof way, like I said I am new to android I really have no idea about everything, and most of them too are initial I don't even know what the initials means. Anyone? Thanks
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
Click to expand...
Click to collapse
I came from an iphone as well, about 2 weeks ago. I used the method posted in my previous reply. It worked for me, and has been doing fine so far. One thing you must do is make sure busybox is installed before you try it though. If you dont have busybox installed, none of the commands will work. Then just download "Terminal Emulator" from the market, and use that to give commands.
Sent from my SAMSUNG-SGH-I997 using XDA App
Cohdee said:
I came from an iphone as well, about 2 weeks ago. I used the method posted in my previous reply. It worked for me, and has been doing fine so far. One thing you must do is make sure busybox is installed before you try it though. If you dont have busybox installed, none of the commands will work. Then just download "Terminal Emulator" from the market, and use that to give commands.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
What command? I really have no idea, can you give me step by step if you don't mind?
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
Alright, I'm hoping I can get some quick useful feedback on this. I'm currently on AOKP Official Milestone 6, and every time I reboot it reverts me settings I had on August 28th. I've been going thru this all day long, Google searching, scanning forums for our device and the T989.
I've attempted Odin flashes 13 times today to go back to Stock Gb and Stock Ics, the flashes show successful, yet AOKP boots right back up. Recovery does nothing to wipe, currently on Clockworkmod Touch Recovery.
Formatting all caches and partitions, Dalvik wipes all 5x each do nothing, even flashing something after this does nothing. I can't even reset AOKP, it takes me right back to the same condition from August 28th, same theme, apps, etc, all there. I've even formatted both emmc and sdcard, nothing. Whatever I do gets overwritten to the previous condition.
Can someone please help me out with this. I'm not even sure what to classify an issue like this as.
Sent from my SGH-I727 using xda premium
you are not the only one who had this issue, its a failure to write to the nand, for the lack of a better word, i have some links in my ref sticky, 1st link in my sig, under the info section on other users who had this problem, one thing i don't think they tried is using adb to push files
edit: damn i forgot to add those posts to my sticky, i/ll search for them and post them up
EDIT: here is one , couldnt find the other one http://forum.xda-developers.com/showthread.php?t=1751338
Thanks a lot man, what exactly causes something like this to happen? Is it Galaxy specific?
Sent from my SGH-I727 using xda premium
KillaT21 said:
Thanks a lot man, what exactly causes something like this to happen? Is it Galaxy specific?
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
it seems to be a ram hardware failure, but unless i had the problem myself, cant rule out user error, dev's write and wipe the phones constantly, and ive only seen it happen to two users.
read this http://forum.xda-developers.com/showthread.php?t=1704646 and see if it applies to you.
or you can try to push files through adb if phone accepts an adb connection, never tried it so cant help you there
vincom said:
it seems to be a ram hardware failure, but unless i had the problem myself, cant rule out user error, dev's write and wipe the phones constantly, and ive only seen it happen to two users.
read this http://forum.xda-developers.com/showthread.php?t=1704646 and see if it applies to you.
or you can try to push files through adb if phone accepts an adb connection, never tried it so cant help you there
Click to expand...
Click to collapse
I don't think it applies 100% to me. I can write to system, it just gets ignored lol. I read that Mightyoj had the exact issue and adb did nothing for him. I'm within my 30 days, I may need to either find another way to hard brick it or call at&t like he did.
Regardless, thanks for your help Vincom.
Sent from my SGH-I727 using xda premium
Your phone got "lost" / "stolen"
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
vincom said:
or you can try to push files through adb if phone accepts an adb connection, never tried it so cant help you there
Click to expand...
Click to collapse
I remember this issue. The guy who's post you linked to did try adb to no luck. The only thing I can think to try through adb is changing the permissions of emmc? Some one with more knowledge then me might chime in but I'd say
Code:
adb shell
chmod 666 /emmc
That should give read/write to emmc if it will stick. Again you might want to get confirmation on this before attempting it as it is my best guess for your issue. If it's a bad nand you may just be SOL.
Illnevertell said:
Your phone got "lost" / "stolen"
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
There's a thought...hmm
Sent from my SGH-I727 using xda premium
All right, after a few weeks of headache, I thought I'd update this thread as to whats going on.
Sent my phone off to Samsung twice for a fix. Twice due to the support rep not having any clue what the issues were that I was describing to her the first time over, so they sent it back in the same condition as when I sent it to them. Their solution: Applied stock SW.
They didnt even attempt to turn it on to see if the issue was resolved. So fast forward to 3 days after receiving it back and I called Samsung back and carefully worded my problem again and pointed out that I sent it to them before and no solution was found.
So I sent it back off, and 3 days later they called me asking me what exactly was wrong with my phone and I mentioned that it was some issue with the internal memory upon boot that locked everything into a specific setting from August 28th, and that it must be hardware related. She said she would inform the technicians.
So finally, I got my service ticket and the solution they reached was:
Replaced PBA, which is the Print Board Assembly. Looked around on Xda and for the definition and found that a few Samsung devices that were having similar issues as myself and a few others were remedied by replacing it. Currently waiting on them to reship it to me.
So, the "moral" of the story is, if you are within your Manufacturers warranty with Samsung, give Support a call and try as best as you can to explain your problem to them, but dont let them know you're rooted. They are not "supposed" to troubleshoot/fix your issue when rooted. But when they get hands on, they know that the average person that roots would have likely reversed any software issues/damage aside from a brick.
Hopefully this tidbit of information can help future Androidians with Samsung Devices on whats going on and expedite their efforts for a solution. Thanks again to all that were involved
Sent from my SGH-I997 using xda premium
Hey folks, I've been doing some reading on the topic this morning and found some good options but need a few more specifics and maybe some extra expert opinion. Something is awry with my USB port - It will charge but cannot get it to recognize the presence of the computer. It also goes through seasons where it rapidly toggles back and forth to/from dock mode.
Basic facts/stats:
SGS3 verizon, SCH-I535, running 4.0.4 I535VRLF2.
Rooted, Stock ROM, never unlocked bootloader.
Running CWM Recovery v5.5.0.4
I'm trying to restore to a point where I can do a warranty return for the hardware issue without being dinged for software mods.
So I think my options are these.. Feedback?
Mobile Odin... but don't want to unlock the bootloader, seems to be a step in the wrong direction.
ABD Wifi
Terminal emulator on the phone
Here's a thread that I found helpful...
http://forum.xda-developers.com/showthread.php?p=27206637&postcount=5
So, finally, my questions that I haven't been able to find an answer to...
Anyone know where can I find the stock recovery image? Not hard to find an image for the whole system, but why flash the whole kit'n'kabodle when you only need the one part?
If I was going to go the ABD/terminal route, is this the correct command? dd if=location of image of=/dev/block/mmblk0p22. This is the location for the Galaxy S2, but not sure if it is correct for S3.
Thanks guys, definitely don't want to make a mistake here in this crippled situation.
xaris1 said:
Hey folks, I've been doing some reading on the topic this morning and found some good options but need a few more specifics and maybe some extra expert opinion. Something is awry with my USB port - It will charge but cannot get it to recognize the presence of the computer. It also goes through seasons where it rapidly toggles back and forth to/from dock mode.
Basic facts/stats:
SGS3 verizon, SCH-I535, running 4.0.4 I535VRLF2.
Rooted, Stock ROM, never unlocked bootloader.
Running CWM Recovery v5.5.0.4
I'm trying to restore to a point where I can do a warranty return for the hardware issue without being dinged for software mods.
So I think my options are these.. Feedback?
Mobile Odin... but don't want to unlock the bootloader, seems to be a step in the wrong direction.
ABD Wifi
Terminal emulator on the phone
Here's a thread that I found helpful...
http://forum.xda-developers.com/showthread.php?p=27206637&postcount=5
So, finally, my questions that I haven't been able to find an answer to...
Anyone know where can I find the stock recovery image? Not hard to find an image for the whole system, but why flash the whole kit'n'kabodle when you only need the one part?
If I was going to go the ABD/terminal route, is this the correct command? dd if=location of image of=/dev/block/mmblk0p22. This is the location for the Galaxy S2, but not sure if it is correct for S3.
Thanks guys, definitely don't want to make a mistake here in this crippled situation.
Click to expand...
Click to collapse
Your on ICS. I would just use EZ-unlock 1.2 and unlock. Takes about about 30 seconds. If flash counter is tripped use free Triangle Away here on XDA to reset it. Another minute. Then use Mobile Odin to flash back full stock image. About 10 minutes. Done.
xaris1 said:
Hey folks, I've been doing some reading on the topic this morning and found some good options but need a few more specifics and maybe some extra expert opinion. Something is awry with my USB port - It will charge but cannot get it to recognize the presence of the computer. It also goes through seasons where it rapidly toggles back and forth to/from dock mode.
Basic facts/stats:
SGS3 verizon, SCH-I535, running 4.0.4 I535VRLF2.
Rooted, Stock ROM, never unlocked bootloader.
Running CWM Recovery v5.5.0.4
I'm trying to restore to a point where I can do a warranty return for the hardware issue without being dinged for software mods.
So I think my options are these.. Feedback?
Mobile Odin... but don't want to unlock the bootloader, seems to be a step in the wrong direction.
ABD Wifi
Terminal emulator on the phone
Here's a thread that I found helpful...
http://forum.xda-developers.com/showthread.php?p=27206637&postcount=5
So, finally, my questions that I haven't been able to find an answer to...
Anyone know where can I find the stock recovery image? Not hard to find an image for the whole system, but why flash the whole kit'n'kabodle when you only need the one part?
If I was going to go the ABD/terminal route, is this the correct command? dd if=location of image of=/dev/block/mmblk0p22. This is the location for the Galaxy S2, but not sure if it is correct for S3.
Thanks guys, definitely don't want to make a mistake here in this crippled situation.
Click to expand...
Click to collapse
The same thing happened with my first S3, I used mobile odin and flashed back to stock and sent it into verizon for my replacement and this was a couple months ago. I would suggest that route.
Can't post outside links yet, but search for this on youtube..
How To Unroot Galaxy S3 Verizon/AT&T/Sprint/T-mobile - Flash Stock Rom & Fix Warranty
http://www.youtube.com/watch?v=vVVHRyDb4IQ
Nice little video guide for mobile odin.
Have you tried a different USB cable? I've had the same problem and a new cable worked wonders.
Sent from my SCH-I535 using xda app-developers app
cmb3497 said:
Have you tried a different USB cable? I've had the same problem and a new cable worked wonders.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Several, and the cables work with my old phone w/ no problems. Reinstalled the samsung drivers. I'm pretty sure that it's the USB due to the issue with rapid toggling in/out of dock mode. A quick squirt of compressed air fixes the dock mode issue but there are still periodic re-occurrences.
Downloading the stock firmware now. I'll keep you all posted. Thanks a ton for the advice.
Try the xperia x8 drivers. I can't get the Samsung ones to connect for anything. I haven't had an issue since ditching the Samsung ones.
I had the same problems, constant toggling. Just my opinion, it's a driver issue.
Sent from my SCH-I535 using xda app-developers app
prdog1 said:
Your on ICS. I would just use EZ-unlock 1.2 and unlock. Takes about about 30 seconds. If flash counter is tripped use free Triangle Away here on XDA to reset it. Another minute. Then use Mobile Odin to flash back full stock image. About 10 minutes. Done.
Click to expand...
Click to collapse
THANKS man, your guidance got me there without a hitch. Really appreciate it. Samsung is shipping me a new S3, now this one will be ready to return.
bobAbooE said:
Try the xperia x8 drivers. I can't get the Samsung ones to connect for anything. I haven't had an issue since ditching the Samsung ones.
I had the same problems, constant toggling. Just my opinion, it's a driver issue.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Gave it a try but it didn't work. Thanks anyway man.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Hi Im a complete Noob for doinf this :silly:
Coming from Htc One there was a method posted on the Htc one forums to get the bootloader locked.
http://forum.xda-developers.com/showthread.php?t=2475914
And stupid me without thinking I used the command echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
to reset the unlocked to lock stats.
Well now the phone doesnt even turn on no booloader no recovery nothing, pc detects it as an unkown device but I dont know what to do with it.
is there anyway possible to bring this brick back to life or do i have send it back to google?
Any suggestions or Advice is welcome.
Thanks
If it doesn't turn on I think you're hosed. You messed up one the partitions running the commands you did Please read the pinned (stickies) threads on the general forum before you do anything on your new device.
You wiped an important partition of the phone, and now it won't boot. Looks like you are out of luck. You can probably call Google and tell them your phone won't turn on, but technically that would be lying because you broke it without reading.
If you do get a replacement, and want to unlock the bootloader just get fastboot and type 'fastboot oem unlock'. That's it. This is a Nexus.
You kinda asked for it by attempting to follow a guide that is not for your device. HTC One =/= Nexus 5.
Like the above said, you wiped a partition essential to the function of your device. No way to fix it. Gonna have to send it back to Google, hopefully when you do they won't charge you and will just send you another. They might be used to having a million returns because when a device launchers there is a massive amount of nitpicking customers trying to get replacements and/or their are legit issues with the devices and they won't bother to check whats wrong with your phone. Most likely they will though, and who knows what you'll be charged. Good luck!
xXxG0dzRAgexXx said:
You kinda asked for it by attempting to follow a guide that is not for your device. HTC One =/= Nexus 5.
Like the above said, you wiped a partition essential to the function of your device. No way to fix it. Gonna have to send it back to Google, hopefully when you do they won't charge you and will just send you another. They might be used to having a million returns because when a device launchers there is a massive amount of nitpicking customers trying to get replacements and/or their are legit issues with the devices and they won't bother to check whats wrong with your phone. Most likely they will though, and who knows what you'll be charged. Good luck!
Click to expand...
Click to collapse
I hope I do get a replacement , Im in the Uk so i cant get in contact with Google support till Monday now. I was stupid for doing that and I have learned a valuable lesson.
That's what happens when you do not read. Good luck.
xXxG0dzRAgexXx said:
You kinda asked for it by attempting to follow a guide that is not for your device. HTC One =/= Nexus 5.
Like the above said, you wiped a partition essential to the function of your device. No way to fix it. Gonna have to send it back to Google, hopefully when you do they won't charge you and will just send you another. They might be used to having a million returns because when a device launchers there is a massive amount of nitpicking customers trying to get replacements and/or their are legit issues with the devices and they won't bother to check whats wrong with your phone. Most likely they will though, and who knows what you'll be charged. Good luck!
Click to expand...
Click to collapse
this just scares me about android. I am getting a nexus 5 soon, and love tweaking with my phones, so im pretty sure theres nothing to worry about, but still.... not trying to troll or anything, but on iPhone, its ridiculously hard to "hard brick". I've seen posts online, but most of the time its just users who end up thinking they've done a fix with no result, when in reality, ive had to fix plenty of iphones in the past, and some have come in horribly screwed up. always been able to fix them and restore though, even if it meant wiping a users data. With android, while I understand there are options to restore and such, it still seems rather easy to totally brick if you miss a step or something were to happen.
hoping I will never have this issue.... :-\
unvaluablespace said:
this just scares me about android. I am getting a nexus 5 soon, and love tweaking with my phones, so im pretty sure theres nothing to worry about, but still.... not trying to troll or anything, but on iPhone, its ridiculously hard to "hard brick". I've seen posts online, but most of the time its just users who end up thinking they've done a fix with no result, when in reality, ive had to fix plenty of iphones in the past, and some have come in horribly screwed up. always been able to fix them and restore though, even if it meant wiping a users data. With android, while I understand there are options to restore and such, it still seems rather easy to totally brick if you miss a step or something were to happen.
hoping I will never have this issue.... :-\
Click to expand...
Click to collapse
iPhone's are pretty much impossible to hard brick. Was in the jailbreak scene for 2 and a half years, and there is no way to hard brick one. Very early on it was possible, but not anymore. Android devices are pretty hard to brick usually. Just make sure you follow a guide for your device and all should be well. Only risky thing really is flashing the wrong firmware or radio on a device. Flashing roms, mods, or wiping the entire device is always fixable (not important partitions though, but that's only possible via command terminal like in this case). I was at first scared with my HTC One since it was my first android device, but realized as long as you know what your doing all should go well.
unvaluablespace said:
this just scares me about android. I am getting a nexus 5 soon, and love tweaking with my phones, so im pretty sure theres nothing to worry about, but still.... not trying to troll or anything, but on iPhone, its ridiculously hard to "hard brick". I've seen posts online, but most of the time its just users who end up thinking they've done a fix with no result, when in reality, ive had to fix plenty of iphones in the past, and some have come in horribly screwed up. always been able to fix them and restore though, even if it meant wiping a users data. With android, while I understand there are options to restore and such, it still seems rather easy to totally brick if you miss a step or something were to happen.
hoping I will never have this issue.... :-\
Click to expand...
Click to collapse
Don't be too scared. Honestly bricking a nexus device is quite hard as long you are somewhat literate. With most situations (if you have access to the bootloader) you have the option of flashing the factory images which will get your phone up and running 95% of the time. Basically if you can access the bootloader, there is nothing to panic or worry about.
The only reason this guy bricked his phone is because he thought it was a good idea to root his nexus 5 using a guide that teaches you how to unlock the bootloader on an HTC One.
Just make sure you read a bit, understand what you are doing, and don't blindly follow random instructions that you find on the interwebz. If you follow that advice i doubt you will have any problems.
Sent using xda-developers app
uronfire said:
Hi Im a complete Noob for doinf this :silly:
Coming from Htc One there was a method posted on the Htc one forums to get the bootloader locked.
http://forum.xda-developers.com/showthread.php?t=2475914
And stupid me without thinking I used the command echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
to reset the unlocked to lock stats.
Well now the phone doesnt even turn on no booloader no recovery nothing, pc detects it as an unkown device but I dont know what to do with it.
is there anyway possible to bring this brick back to life or do i have send it back to google?
Any suggestions or Advice is welcome.
Thanks
Click to expand...
Click to collapse
Still having issues? I've got a couple of ideas you could try. I managed to fix my nexus after I completely screwed up the bootloader, willing to share how I fixed it
daniel.kusy said:
Still having issues? I've got a couple of ideas you could try. I managed to fix my nexus after I completely screwed up the bootloader, willing to share how I fixed it
Click to expand...
Click to collapse
How did you manage to fix yours? Mine's still bricked but can only get access to the bootloader. Have tried every option of flashing factory but still no luck.
How do you brick a Nexus?
I wish I could feel pity but man....
Tell them it won't turn on. Send it back I'm sure they won't know. Hope they don't at least. Better than keeping a paperweight.
sent from my Nexus 5
jphilippon said:
How do you brick a Nexus?
I wish I could feel pity but man....
Tell them it won't turn on. Send it back I'm sure they won't know. Hope they don't at least. Better than keeping a paperweight.
sent from my Nexus 5
Click to expand...
Click to collapse
I used ChainFires auto root and it quite simply did not work and bricked my phone. Nothing else to it… it just bricked my N5. No interruptions, all correct drivers installed. Now I'm stuck with a phone displaying unlocked boot loader (which I can lock temporarily using fast boot command.) but when the device restarts into fast boot it's back saying unlocked. Nightmare really.
Meakii said:
I used ChainFires auto root and it quite simply did not work and bricked my phone. Nothing else to it… it just bricked my N5. No interruptions, all correct drivers installed. Now I'm stuck with a phone displaying unlocked boot loader (which I can lock temporarily using fast boot command.) but when the device restarts into fast boot it's back saying unlocked. Nightmare really.
Click to expand...
Click to collapse
there is a person in the franco's thread who even corrupted the bootloader he managed to recover using some lg flsh tool something like kdz
it was some kind of methord used to unbrick nexus 4
Meakii said:
How did you manage to fix yours? Mine's still bricked but can only get access to the bootloader. Have tried every option of flashing factory but still no luck.
Click to expand...
Click to collapse
have you tried the flash-all.bat (factory image using command prompt from the sdk/platform-tools folder )?
Sent from my Nexus 5 using Tapatalk
floxrin said:
have you tried the flash-all.bat (factory image using command prompt from the sdk/platform-tools folder )?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yea mate. No luck.
Meakii said:
Yea mate. No luck.
Click to expand...
Click to collapse
If you can get into bootloader does fastboot work? If you can get into the bootloader virtually anything can be fixed. What happens when you click the flash all.bat file?
Try LG download mode
Sent from my Nexus 5 using Tapatalk
daniel.kusy said:
If you can get into bootloader does fastboot work? If you can get into the bootloader virtually anything can be fixed. What happens when you click the flash all.bat file?
Click to expand...
Click to collapse
See the attached. I can't do anything. Every attempt to write anything to the internal SD fails. I wish it could be fixed but have tried everything. Worst part is even after fastboot oem lock cmd when it restarts it's unlocked again. Meaning when I return it warranty will probably be void.
This guy has the same problem. http://forum.xda-developers.com/showthread.php?p=315800
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
okay i upgraded to 4.3 OTA and tried to revert back and soft bricked my phone. I still have access to download mode and the stock recovery. I know now that i can not revert but is there any way of getting it back to 4.3 so i can have a phone again?
thanks for the future help.
This is similar what happened to me. I have never done anything with my phone as far as rooting and I tried reverting to stock 4.1.2. In Odin I kept getting the "Nand Start! Fail (Auth)" because of the locked bootloader I guess. I flashed some other firmware that was unofficial with the locked bootloader and now I get the "unauthorized software detected" and I cant do anything but enter Odin download mode. What should I do?
that is exactly what is happing to me. same error and all.
Once you took the OTA 4.3 you got locked in. No way of going back.
Sent from my SCH-I535 using Tapatalk
I dont want to go back just get rid of the soft brick so i can use it
im having the same problem and need to get it fixed please help anyone???!!!! im leaving for florida in two days and have nothing else. HELP!!!!
If you took the OTA and tried to flash 4.1.2 Odin or unlock bootloader you are Hard bricked , no method or recovering it yet.
If you have stock recovery and download mode , only hope is wait for 4.3 .tar file
Theres no custom recovery I can flash and flash some other software or something?
Elemt said:
Theres no custom recovery I can flash and flash some other software or something?
Click to expand...
Click to collapse
Nope , once you take 4.3 OTA you done , no flashing anything. And once you try to flash recovery or revert to older software you are bricked.
Sorry to be the bear of bad news.
There is a full thread of why and how so many devices have been bricked
http://forum.xda-developers.com/showthread.php?t=2575661
jlyle said:
Nope , once you take 4.3 OTA you done , no flashing anything. And once you try to flash recovery or revert to older software you are bricked.
Sorry to be the bear of bad news.
There is a full thread of why and how so many devices have been bricked
http://forum.xda-developers.com/showthread.php?t=2575661
Click to expand...
Click to collapse
Do you know if anyone is working on a fix? or a .tar file of 4.3?
dvdavid2 said:
Do you know if anyone is working on a fix? or a .tar file of 4.3?
Click to expand...
Click to collapse
Thanks for the info. hopefully a fix will be done soon. And do you know how i should keep to see when the work around is finished .
thanks in advanced guys.
This might give you a chance to unbrick.... possibly
http://forum.xda-developers.com/showthread.php?t=2581166
I got the "unauthorised software detected" on my phone like 3 days ago from messing up on a recovery and all I did was go into the Verizon store and said idk what happened and they called technical support and they asked me if I flashed software on my phone and I just said "no, I just plugged it into my laptop and it did this" so they said they will just send me a new sgs3 and I just got it today.
Pretty simple.
And I don't have insurance .
Hit thanks if I helped
Sent from my SCH-I535 using xda app-developers app
ScubaSteev said:
I got the "unauthorised software detected" on my phone like 3 days ago from messing up on a recovery and all I did was go into the Verizon store and said idk what happened and they called technical support and they asked me if I flashed software on my phone and I just said "no, I just plugged it into my laptop and it did this" so they said they will just send me a new sgs3 and I just got it today.
Pretty simple.
And I don't have insurance .
Hit thanks if I helped
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Funny thing is Verizon can tell if phone was hacked with, and can choose to add the cost of phone to your bill so this method is not highly recommended.
Sent from my SCH-I535 using xda app-developers app
jlyle said:
Funny thing is Verizon can tell if phone was hacked with, and can choose to add the cost of phone to your bill so this method is not highly recommended.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Any break throughs????
dvdavid2 said:
Any break throughs????
Click to expand...
Click to collapse
None that I have seen
Sent from my SCH-I535 using xda app-developers app
jlyle said:
Funny thing is Verizon can tell if phone was hacked with, and can choose to add the cost of phone to your bill so this method is not highly recommended.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Not to mention it is basically fraud, and is the main reason Verizon decided to start locking down phones in the first place.
I understand everyone is taking risks when flashing custom, and flashes can go wrong even when you do everything right, but there is VERY little chance of bricking your phone if you take your time and do a bit of research before you hit any buttons. And if you do manage to brick your phone, man up and pay for a new phone or pay for it to be fixed. Otherwise stop treating your $600 piece of technology like a toy.
BattsNotIncld said:
Not to mention it is basically fraud, and is the main reason Verizon decided to start locking down phones in the first place.
I understand everyone is taking risks when flashing custom, and flashes can go wrong even when you do everything right, but there is VERY little chance of bricking your phone if you take your time and do a bit of research before you hit any buttons. And if you do manage to brick your phone, man up and pay for a new phone or pay for it to be fixed. Otherwise stop treating your $600 piece of technology like a toy.
Click to expand...
Click to collapse
The first time I ever rooted, I was worried about bricking. So i read everything I could find relevant.
Why in the world anyone would flash without reading is beyond me. Every single thread in Verizon Galaxy S3 at least mentions, if not totally devoted, to how bad 4.3 is and if you flash something on it you will brick.
I just don't get it.
Sent from my Last Ever Samsung Device.
If you do a battery pull and start back up in download mode (might take a couple of times to get it to work) then use the Verizon software upgrade assistant it should fix it but you will be stuck with 4.3. Worked for me