hello....
i need original 2.3.3 vodafone rom. i;ve updated the rom and now my phone has screen problems and i need to return it for warranty issues.
where can i get i9001bukg1, plzzz!!?!?!?
i really need it
Did you get the BUKG1 ROM?
I could help you if dumping is not dangerous.
Just let me know how.
hey... i have a clean phone running with i9001bukg1, but atm i even cannot access the recovery mode. so, no idea how to make it available for anybody else...
[edit] forget it - did a kies-update and since that i have another firmware.
I took over a hard bricked phone Verizon S3. The previous owner said he tried to Odin the phone to restore it to stock, but the phone went dead. So I suspect he may have flashed the phone with a wrong ROM from another phone.
Since that was a while ago, I figure the bootloader was still unlockable. So the entire phone, from bootloader, to system, modem, etc., was re-written with the new ROM. I tried the SD card method, but no luck at all.
Anyone is a similar situation? I heard some people flashed with the GT-I9300 ROM. Also, some folks purposely flashed ROM from other phone and have some luck.
My question is that, what I should try to unbrick this phone. If the wrong ROM is from GT-I9300, should I build a I-9300 SD card and try to boot off its bootloader? Or the phone is totally dead?
The other problem is that, I do not know exactly what ROM the previous owner flashed with....
BaSingSe said:
I took over a hard bricked phone Verizon S3. The previous owner said he tried to Odin the phone to restore it to stock, but the phone went dead. So I suspect he may have flashed the phone with a wrong ROM from another phone.
Since that was a while ago, I figure the bootloader was still unlockable. So the entire phone, from bootloader, to system, modem, etc., was re-written with the new ROM. I tried the SD card method, but no luck at all.
Anyone is a similar situation? I heard some people flashed with the GT-I9300 ROM. Also, some folks purposely flashed ROM from other phone and have some luck.
My question is that, what I should try to unbrick this phone. If the wrong ROM is from GT-I9300, should I build a I-9300 SD card and try to boot off its bootloader? Or the phone is totally dead?
The other problem is that, I do not know exactly what ROM the previous owner flashed with....
Click to expand...
Click to collapse
If the phone still get to Download Mode, you can try to Flash through Odin or if it can go to Recovery Mode, try to Flash any rom. If it's actually dead, maybe there is anyone that can help you but actually they exchange their labor to cash.
Long story short...
I have the Verizon version of this tab and was running a custom rom for the past year. Tonight I flashed back to stock and rerooted. I thought the bootloader was still unlocked but apparently it's not. I tried to flash a recovery and failed. Tried to unlock bootloader and failed with the only image I could find to do so.
So I'm left with a device that gives me an "unsupported...take to Verizon" message when I try to boot into recovery. I can still boot into download and get into the OS that way though.
This device isn't that big a deal to me and I don't plan on flashing anything in the future. Is not having a workable recovery going to be a problem?
66 views and nobody can tell me whether I need to fix this or not? That's all I'm asking. If I'm not planning on flashing anything again do I need to worry about not having a working recovery?
If you are not intending on flashing any roms on it and if your tab is booting fine and working well on stock then you have no need to worry about it...
Sent from my GT-P3100 using Tapatalk
Out of curiosity, is there way to brick this device to stage that for example warranty service can`t find out that it is self-inflicted?
Surely, flashing a bootloader not intended for the device is the best way to brick it?
i will do in that way :
flash engeniereng bootloader
flash a rom not suitable for your device ( ex. rom for 9200hk )
if still works, flash wrong pit file or modified wrong one )
Why would someone do that anyway???
XxM4tzexX said:
Why would someone do that anyway???
Click to expand...
Click to collapse
I can tell you why someone would do that. This is purely hypotethical but here is one reason. Let´s say that you have rooted your device and lost your warranty. After that your camera starts to make buzzing noise and focusing don´t work. ie. this case: http://forum.xda-developers.com/galaxy-s6/help/galaxy-s6-camera-randomly-makes-loud-t3123724
Now you want to get that camera fixed for warranty, but they don´t accept it because Knox is tripped. But now if whole phone is bricked and be sent to warranty service, they have no other choice but flash stock firmware and untrip Knox and device will gain full warranty again. Or that is my theory anyway. I mean sometimes these devices just stop working maybe due faulty motherboard or something similar. Please remember this is totally hypotethical...
PeK_m said:
I can tell you why someone would do that. This is purely hypotethical but here is one reason. Let´s say that you have rooted your device and lost your warranty. After that your camera starts to make buzzing noise and focusing don´t work. ie. this case: http://forum.xda-developers.com/galaxy-s6/help/galaxy-s6-camera-randomly-makes-loud-t3123724
Now you want to get that camera fixed for warranty, but they don´t accept it because Knox is tripped. But now if whole phone is bricked and be sent to warranty service, they have no other choice but flash stock firmware and untrip Knox and device will gain full warranty again. Or that is my theory anyway. I mean sometimes these devices just stop working maybe due faulty motherboard or something similar. Please remember this is totally hypotethical...
Click to expand...
Click to collapse
Dark ideas! I like it!
I bricked my G920F trying to get back to stock-rom. Nothing would work, Odin failed time after time (cm.bin). I could flash TWRP and used ADB to get back to stock-recovery, connected to smart-switch and performed emergency restore. Failed again.
I took it to a Samsung servicepoint (talking about Holland) and they immediatly found the custom flag. Phone wil be send over to Samsung now and, according to the lady at the servicepoint, Samsung does not even check. They just reflash it and send it back under full waranty. All I can do now is hoping she is right....
Still figuring out why everybody but me can restore a bricked phone through ODIN.
Edit: I got it back to proper firmware, but now have an issue with re-locking the bootloader so that I can install an OTA and make my sim card recognizable again. "Still waiting for signed boot.img"; can anybody provide a DL link to a signed boot.img for my specific model? [PCO29.114-54-2]
I'll try to keep this short and simple. It's my first post to these forums (hi), so sorry if I say stuff that sounds really simple or silly.
So, for a while now, I was dealing with a lot of really minor issues on my phone that I was told by those I asked was corruption in the android stock firmware. It wasn't anything major, but the issues were building up, and factory resets weren't fixing any of them. So, with my phone already out of warranty, I decided there wouldn't be any harm in trying to fix it myself. After reading up on it a little, I unlocked my bootloader, then I decided I would try flashing a custom ROM.
Well... I didn't even get that far. I was trying really hard to use the TWRP to back up my phone, but it kept getting errors. Looking it up, people said you just have to delete corrupted files to make it work, so I went back and forth wiping the files that gave it issues, until eventually I just decided to give up because there were so many corrupted files, just in the boot folder alone. When I went to turn the phone on and throw in the towel... I got the dreaded bootloop.
I freaked out, and decided that since I could still get into fastboot mode, I would try to stock the flash firmware to fix it. So, I went online, just found stock firmware, ran a batch file that did it all automatically, and...
When I turned my phone on, it was for the complete wrong carrier. Previously, it was a device I bought from T-Mobile, and thus, I was using a sim card and all that from them. Now the device is tied to Cricket, and so, of course, that stuff doesn't work.
Weirdly, there's other issues on the device now too, like when trying to add a Google account, the phone just closes out of everything...
Well.
I do know there's a guide here for how to flash the phone back to original firmware (although they don't have my firmware (M3DE6) listed), but there's other issues now, too. Stuff like the IMEI are totally wiped from the phone's memory now, just being listed as "Unknown" in the phone's settings. Not to mention, everytime I turn on the phone, I get text that says "bad ID" and it takes an additional 10-15 seconds to turn on. Is there any way to fix all this stuff? I don't mind if I have to restore it to OG stockware or if flashing a custom ROM will fix the problem- I just really need my phone to be able to work with my sim card again so I can take and make calls/texts.
I've still got to pay on my phone for a year still via the contract I made with T-Mobile, so it'd really suck if my phone got stuck in an unusable condition like this. If there's anybody who could just help me get it back to WORKING condition (calls/texts, google accounts, etc.), then I would greatly appreciate that. Thanks.
Tsukomasi said:
I'll try to keep this short and simple. It's my first post to these forums (hi), so sorry if I say stuff that sounds really simple or silly.
So, for a while now, I was dealing with a lot of really minor issues on my phone that I was told by those I asked was corruption in the android stock firmware. It wasn't anything major, but the issues were building up, and factory resets weren't fixing any of them. So, with my phone already out of warranty, I decided there wouldn't be any harm in trying to fix it myself. After reading up on it a little, I unlocked my bootloader, then I decided I would try flashing a custom ROM.
Well... I didn't even get that far. I was trying really hard to use the TWRP to back up my phone, but it kept getting errors. Looking it up, people said you just have to delete corrupted files to make it work, so I went back and forth wiping the files that gave it issues, until eventually I just decided to give up because there were so many corrupted files, just in the boot folder alone. When I went to turn the phone on and throw in the towel... I got the dreaded bootloop.
I freaked out, and decided that since I could still get into fastboot mode, I would try to stock the flash firmware to fix it. So, I went online, just found stock firmware, ran a batch file that did it all automatically, and...
When I turned my phone on, it was for the complete wrong carrier. Previously, it was a device I bought from T-Mobile, and thus, I was using a sim card and all that from them. Now the device is tied to Cricket, and so, of course, that stuff doesn't work.
Weirdly, there's other issues on the device now too, like when trying to add a Google account, the phone just closes out of everything...
Well.
I do know there's a guide here for how to flash the phone back to original firmware (although they don't have my firmware (M3DE6) listed), but there's other issues now, too. Stuff like the IMEI are totally wiped from the phone's memory now, just being listed as "Unknown" in the phone's settings. Not to mention, everytime I turn on the phone, I get text that says "bad ID" and it takes an additional 10-15 seconds to turn on. Is there any way to fix all this stuff? I don't mind if I have to restore it to OG stockware or if flashing a custom ROM will fix the problem- I just really need my phone to be able to work with my sim card again so I can take and make calls/texts.
I've still got to pay on my phone for a year still via the contract I made with T-Mobile, so it'd really suck if my phone got stuck in an unusable condition like this. If there's anybody who could just help me get it back to WORKING condition (calls/texts, google accounts, etc.), then I would greatly appreciate that. Thanks.
Click to expand...
Click to collapse
U in USA if so I could try the reuts think that's how it spelled TMobile is same as crickit if I member right so u can flash the retail firm where if u in the states.I on cc but not the firmware for them I'm in the retail version works great no added junk ware either
roadkill42 said:
U in USA if so I could try the reuts think that's how it spelled TMobile is same as crickit if I member right so u can flash the retail firm where if u in the states.I on cc but not the firmware for them I'm in the retail version works great no added junk ware either
Click to expand...
Click to collapse
I did find my device's actual stock firmware from another website and installed it, but now the sim card doesn't work. I've heard that if I perform an OTA update, it'll make it work again, but... I can't perform an OTA update because the bootloader is unlocked. I can't re-lock it, because everytime I try, it gives me a message that says "Still waiting for signed boot.img".
Someone said to use the rescue and smart assistant app, but it doesn't recognize my phone, so that's a no-go.
Tsukomasi said:
I did find my device's actual stock firmware from another website and installed it, but now the sim card doesn't work. I've heard that if I perform an OTA update, it'll make it work again, but... I can't perform an OTA update because the bootloader is unlocked. I can't re-lock it, because everytime I try, it gives me a message that says "Still waiting for signed boot.img".
Someone said to use the rescue and smart assistant app, but it doesn't recognize my phone, so that's a no-go.
Click to expand...
Click to collapse
Have u done the factory reset after flashing the software? U might have to reflash the modem look through this sight or tellagram for how to
roadkill42 said:
Have u done the factory reset after flashing the software? U might have to reflash the modem look through this sight or tellagram for how to
Click to expand...
Click to collapse
I tried a ton of different fixes and approaches, and I still can't get it to work. I'm gonna make a new thread now since I've got a new main issue to deal with. This is... a mess.
Tsukomasi said:
I tried a ton of different fixes and approaches, and I still can't get it to work. I'm gonna make a new thread now since I've got a new main issue to deal with. This is... a mess.
Click to expand...
Click to collapse
Sorry
roadkill42 said:
Sorry
Click to expand...
Click to collapse
Nah, don't worry about it. I'm the one who messed up my phone.
Tsukomasi said:
Nah, don't worry about it. I'm the one who messed up my phone.
Click to expand...
Click to collapse
Here is the bat fille just change the zip to bat then get the retus file I'm looking for the link of the software I used it is lol. https://www.lolinet.com/. Pm me I can tell u how to set it up. https://mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/