[Q] Help me.. How To Install VZW_XT926_4.1.2.xml - RAZR HD Q&A, Help & Troubleshooting

Hello friends I have a problem with my phone : cry : .. past days I made ​​a mistake of firmware and install a rom on my phone of xt925 and is a ' ' xt926 ' ' I need lots of help to return to the rom Original Verizon
VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-4_VQW_CFC.xml
I am trying to install via RSD Lite , but I get the following error appears in the image :crying:
please help dont know what else to do to install the rom on my phone, this unlocked and root for procedures

try this, hope you understand how to use it.

Resp
TOYEP said:
try this, hope you understand how to use it.
Click to expand...
Click to collapse
Thanks buddy , I'll try ... I imagine these are only replacing the I have ..

Js.Vicious said:
Thanks buddy , I'll try ... I imagine these are only replacing the I have ..
Click to expand...
Click to collapse
TOYEP said:
try this, hope you understand how to use it.
Click to expand...
Click to collapse
there is no way to flash an equal version of trust zone with rsd.
he needs to replace all the files anyways.
2 possible solutions come to mind,
1. flash the next newer firmware with rsd, if that fails,
2. flash the same version with Mfastboot, if that fails, try the newer version.
figuring out how to bypass the tz fail is easy, but it will just throw another error when it gets to the next file you cant downgrade or re-write equal. thats why the steps i have suggested should be tried.

bweN diorD said:
there is no way to flash an equal version of trust zone with rsd.
he needs to replace all the files anyways.
2 possible solutions come to mind,
1. flash the next newer firmware with rsd, if that fails,
2. flash the same version with Mfastboot, if that fails, try the newer version.
figuring out how to bypass the tz fail is easy, but it will just throw another error when it gets to the next file you cant downgrade or re-write equal. thats why the steps i have suggested should be tried.
Click to expand...
Click to collapse
yes, he must replace files IF current rom defferent from mine, i use latest stock rom released.
and i assume he know how to put md5-hash to the .xml file if he wish do some experimental :laugh:

Keep in mind he flashed 925 FW to a 926, he could be toast.
Sent from my HTC6525LVW using Tapatalk

correct. i think he stuck at bootloader.

You may be right, but it doesn't hurt to at least try the most correct method to fix it.
Sent from my G3, with mods made possible by team Codefire.

RegiArt exceptional
i think what he got when research with "firmware" or "ROM".. worst case is softbrick. correct?

TOYEP said:
i think what he got when research with "firmware" or "ROM".. worst case is softbrick. correct?
Click to expand...
Click to collapse
not really, depending on what files flash, if not all, it surely could be toast also.

Related

[Q] flashing Galaxy S4.. PLEASE HELPP

hello,
i rooted my galaxy s4 and ever since that, i keep getting the error "system UI has stopped".. so after doing a lot of research i found that only way to fix this is by flashing stock rom. so i need to flash UCUEMK2 into my SGH-I337 AT&T phone via odin. im not sure if i should include a PIT file along with the AP file? what should i do?
i dont want to brick this phone again, so someone please help me..
i would really appreciate your help. thank you!
luckyd8 said:
hello,
i rooted my galaxy s4 and ever since that, i keep getting the error "system UI has stopped".. so after doing a lot of research i found that only way to fix this is by flashing stock rom. so i need to flash UCUEMK2 into my SGH-I337 AT&T phone via odin. im not sure if i should include a PIT file along with the AP file? what should i do?
i dont want to brick this phone again, so someone please help me..
i would really appreciate your help. thank you!
Click to expand...
Click to collapse
if you download your stock rom from sammobile or samsungupdates, it will include only the necessary files. if it includes a .pit, use it, otherwise dont. (usually there isnt one)
Kobro said:
if you download your stock rom from sammobile or samsungupdates, it will include only the necessary files. if it includes a .pit, use it, otherwise dont. (usually there isnt one)
Click to expand...
Click to collapse
Sammobile and other sites only have the 4.2.2 version, my phone has the ver 4.3 which i prefer.. So i should include the PIT file? And what are the chances or bricking this phone? Because im just after getting it fixed from a hard brick.. Thank you for your reply
luckyd8 said:
Sammobile and other sites only have the 4.2.2 version, my phone has the ver 4.3 which i prefer.. So i should include the PIT file? And what are the chances or bricking this phone? Because im just after getting it fixed from a hard brick.. Thank you for your reply
Click to expand...
Click to collapse
how did you update to 4.3? if its a custom rom, you can just flash 4.2.2 again, then install the rom. if its by ota or kies, install 4.2.2 and update the same way again.
Kobro said:
how did you update to 4.3? if its a custom rom, you can just flash 4.2.2 again, then install the rom. if its by ota or kies, install 4.2.2 and update the same way again.
Click to expand...
Click to collapse
I dont think its a custom rom.. After i bricked my old motherboard i bought this new one from ebay.. It had 4.3 pre installed from OTA update i think.. Then i rooted the phone and kept getting the "system ui" error, then i unrooted the phone and hard reset it, didnt fix the problem. So im trying to flash UCUEMK2 which my phone already has.. 4.2.2 has many bugs and i cant send apps to memory card in 4.2.2 thats why im trying to get 4.3.. Thanks
luckyd8 said:
I dont think its a custom rom.. After i bricked my old motherboard i bought this new one from ebay.. It had 4.3 pre installed from OTA update i think.. Then i rooted the phone and kept getting the "system ui" error, then i unrooted the phone and hard reset it, didnt fix the problem. So im trying to flash UCUEMK2 which my phone already has.. 4.2.2 has many bugs and i cant send apps to memory card in 4.2.2 thats why im trying to get 4.3.. Thanks
Click to expand...
Click to collapse
so what i would do if i were in your place is download the 4.2.2. and then upgrate via ot or cutom rom. ill also try finding a 4.3 stock rom for you.
EDIT:
couldnt find 4.3 stock rom, youll have to do one of the above steps
Kobro said:
so what i would do if i were in your place is download the 4.2.2. and then upgrate via ot or cutom rom. ill also try finding a 4.3 stock rom for you.
Click to expand...
Click to collapse
I actually already have the PA file for the 4.3 already downloaded to my laptop but the tutorial i used told me to download the PIT file as well, and the comments that tutorial received werent good, and the other tutorials ive seen never used a pit files.. Thats y im confused.. It would be easy to flash 4.2.2 but the problem is i live in Ireland and we didnt get the 4.3 update here yet and i cant use OTA as its locked to AT&T.. Its very confusing i know.. But thank you so much for helping me
luckyd8 said:
I actually already have the PA file for the 4.3 already downloaded to my laptop but the tutorial i used told me to download the PIT file as well, and the comments that tutorial received werent good, and the other tutorials ive seen never used a pit files.. Thats y im confused.. It would be easy to flash 4.2.2 but the problem is i live in Ireland and we didnt get the 4.3 update here yet and i cant use OTA as its locked to AT&T.. Its very confusing i know.. But thank you so much for helping me
Click to expand...
Click to collapse
well, you can try without the .pit, if it dosent work do it again with, its simple. if you brick it, then use the 4..2.2 to uynbrick then try the other method, so no matter what its not a biggie.
Kobro said:
well, you can try without the .pit, if it dosent work do it again with, its simple. if you brick it, then use the 4..2.2 to uynbrick then try the other method, so no matter what its not a biggie.
Click to expand...
Click to collapse
But what if it hard brick my phone again i hard bricked it before trying to flash something using TWRP .. Then i had to spend €100 on a new motherboard ..
luckyd8 said:
But what if it hard brick my phone again i hard bricked it before trying to flash something using TWRP .. Then i had to spend €100 on a new motherboard ..
Click to expand...
Click to collapse
so try without the pit file, if you brick flash tthe 4.2.2 to unbrick.
what do you mean, you actually had to replace a physical piece because of a brick??? never heard of that happening before
Kobro said:
so try without the pit file, if you brick flash tthe 4.2.2 to unbrick.
what do you mean, you actually had to replace a physical piece because of a brick??? never heard of that happening before
Click to expand...
Click to collapse
Yeah if u hard brick it, the phone doesnt do anything.. Not even charge or flash a light.. Its just completely dead.. You could get it unbricked if ur living in USA or UK and few other countries using JTag method but in ireland they dont have the tools to do it, not even the samsung repair shop, so i had to buy a new motherboard.. Thats why im very scared to do this..
luckyd8 said:
Yeah if u hard brick it, the phone doesnt do anything.. Not even charge or flash a light.. Its just completely dead.. You could get it unbricked if ur living in USA or UK and few other countries using JTag method but in ireland they dont have the tools to do it, not even the samsung repair shop, so i had to buy a new motherboard.. Thats why im very scared to do this..
Click to expand...
Click to collapse
you can also get a usb jig off ebay for about $5, just plug it into the port and it boots into odin mode.
Kobro said:
you can also get a usb jig off ebay for about $5, just plug it into the port and it boots into odin mode.
Click to expand...
Click to collapse
You also have to buy a riff box which is about €140

[Q] Flashing bootloader locked Cricket Moto G/LTE to retail firmware

I want to flash my Cricket Moto G (xt1045) 4.4.4 to the retail 4.4.4 version for a few reasons. Mainly to get access to tethering and the chance that I will be able to update to Lollipop since my hope of cricket releasing the update is fading.
I've been searching around and cannot find a definite answer to this. Lots of people say it should work but I have yet to find anyone who successfully did so. Some say to flash all files but the bootloader and it should be good while others say being the official Motorola firmware everything will flash without a problem.
Has anyone took the plunge and tried it? I would, but I really don't want to be stuck with my Lumia 520 backup phone if I screw something up. Thanks!
macgi77 said:
I want to flash my Cricket Moto G (xt1045) 4.4.4 to the retail 4.4.4 version for a few reasons. Mainly to get access to tethering and the chance that I will be able to update to Lollipop since my hope of cricket releasing the update is fading.
I've been searching around and cannot find a definite answer to this. Lots of people say it should work but I have yet to find anyone who successfully did so. Some say to flash all files but the bootloader and it should be good while others say being the official Motorola firmware everything will flash without a problem.
Has anyone took the plunge and tried it? I would, but I really don't want to be stuck with my Lumia 520 backup phone if I screw something up. Thanks!
Click to expand...
Click to collapse
Anyone? I found a link with instructions but I can't post it until I have 10 posts. If anyone wants to try it, search for "viraj's flash stock rom lock bootloader moto g"
macgi77 said:
Anyone? I found a link with instructions but I can't post it until I have 10 posts. If anyone wants to try it, search for "viraj's flash stock rom lock bootloader moto g"
Click to expand...
Click to collapse
http://dev-viraj.blogspot.in/2015/01/flash-stock-rom-firmware-lock.html
Is that the page? His instructions and ROM download seem to be for a XT1068, not a XT1045. Did you find the ROM files for a 1045 somewhere? I'd like to get access to wifi tethering, too...
Yes, that is the page. I'm assuming the software install would be the same for all models in the Moto G group. The ROM files are located in a thread on here titled "Moto G 4G/LTE Stock Firmware (XT1039/40/42/45)"
Would post a link, but I'm still not allowed.
macgi77 said:
Yes, that is the page. I'm assuming the software install would be the same for all models in the Moto G group. The ROM files are located in a thread on here titled "Moto G 4G/LTE Stock Firmware (XT1039/40/42/45)"
Would post a link, but I'm still not allowed.
Click to expand...
Click to collapse
Link for those looking for it.
Thanks for the link. Maybe I will give this a try, I'm buying an android stereo for my car and need wifi tethering to run the GPS.
If you wind up trying it before I do, let us know! This would theoretically only update the ROM, we'd still be stuck with a locked bootloader, right? If we could find a 4.4.2 ROM, then the Sunshine S-off unlock would work, and we'd be set.
RonnieTheBear said:
Link for those looking for it.
Thanks for the link. Maybe I will give this a try, I'm buying an android stereo for my car and need wifi tethering to run the GPS.
If you wind up trying it before I do, let us know! This would theoretically only update the ROM, we'd still be stuck with a locked bootloader, right? If we could find a 4.4.2 ROM, then the Sunshine S-off unlock would work, and we'd be set.
Click to expand...
Click to collapse
No problem. I will report back if I try, you do the same if you beat me to it! Yes, the bootloader would still be locked, but the software should install since it is an official Motorola signed software. I think I recall reading somewhere that flashing to 4.4.2 would not allow unlocking through sunshine though.
macgi77 said:
No problem. I will report back if I try, you do the same if you beat me to it! Yes, the bootloader would still be locked, but the software should install since it is an official Motorola signed software. I think I recall reading somewhere that flashing to 4.4.2 would not allow unlocking through sunshine though.
Click to expand...
Click to collapse
macgi , I gave this a try last night and the results were extremely not good. Wasn't able to flash the retail firmware, got a bunch of "prevalidation flash failed" on some items, but not others, and then it wouldn't boot. Tried to reflash the cricket firmware to revert back, and got the same prevalidation error for the boot image and the partition gpt.bat file, and now I can't get past the fastboot screen.
RonnieTheBear said:
macgi , I gave this a try last night and the results were extremely not good. Wasn't able to flash the retail firmware, got a bunch of "prevalidation flash failed" on some items, but not others, and then it wouldn't boot. Tried to reflash the cricket firmware to revert back, and got the same prevalidation error for the boot image and the partition gpt.bat file, and now I can't get past the fastboot screen.
Click to expand...
Click to collapse
That sucks. That was the only thing keeping me from trying, the process of fixing it if something screwed up. Hopefully someone has an idea how to fix it since I'm not quite and expert in recoveries.
Thanks for reporting back though!
macgi77 said:
That sucks. That was the only thing keeping me from trying, the process of fixing it if something screwed up. Hopefully someone has an idea how to fix it since I'm not quite and expert in recoveries.
Thanks for reporting back though!
Click to expand...
Click to collapse
Yeah, no problem - it's possible I messed something up in the flashing operation, but I thought you'd want to know.
RonnieTheBear said:
Yeah, no problem - it's possible I messed something up in the flashing operation, but I thought you'd want to know.
Click to expand...
Click to collapse
I'm assuming you tried using the link above? Or did you try flashing each individual file and skipping the bootloader file which was talked about in the firmware thread? (I believe it was around pages 20-30 if I recall)
Found it
@JoeSyr, maybe I'm missing something here specific to Moto G LTE, but flashing a firmware image does not require an unlocked Bootloader. I would do it manually, skip most of the steps, and only flash the system.img initially.
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
The only way you can get into serious trouble would by flashing the motoboot.img (Bootloader) and phone no longer loads fastboot mode. But even then, is there not a hardbrick mbm-ci recovery option for Moto G 4G
Click to expand...
Click to collapse
macgi77 said:
I'm assuming you tried using the link above? Or did you try flashing each individual file and skipping the bootloader file which was talked about in the firmware thread? (I believe it was around pages 20-30 if I recall)
Found it
Click to expand...
Click to collapse
I tried running the ROM Install.bat file the guy put together in the first page you/I linked to, which did attempt to flash the bootloader. It sounds like this person you're quoting is saying the flash should be operational even just flashing those three chunks of the system image file? I think those files wrote okay, but it still didn't boot. Problem might be with this other partition file i mentioned.
RonnieTheBear said:
I tried running the ROM Install.bat file the guy put together in the first page you/I linked to, which did attempt to flash the bootloader. It sounds like this person you're quoting is saying the flash should be operational even just flashing those three chunks of the system image file? I think those files wrote okay, but it still didn't boot. Problem might be with this other partition file i mentioned.
Click to expand...
Click to collapse
That's what it sounds like. Any luck restoring the phone yet?
no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.
RonnieTheBear said:
no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.
Click to expand...
Click to collapse
Good luck, let us know how you make out.
RonnieTheBear said:
no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.
Click to expand...
Click to collapse
Any update?
macgi77 said:
Any update?
Click to expand...
Click to collapse
I tried flashing with some more tools, different firmwares, and different combinations of commands, no luck.
I found a guy in the stock firmware thread that had the exact same problem as me, and has the same cid as my phone, cid 10, which no one else seems to have. They think it might be why the preflash validation failed.
Other users suggested that if a cricket lollipop firmware image is developed at some point in the future, that would be able to flash without error. I reached out to the user to see if he ever resolved it, but didn't get a response.
Anyway, the sense that I got is that my problems were because my cid didn't match. Is yours cid 10 as well? you can check from adb. If it's not, you might be fine attempting it.
It's been a while since I checked, but I believe it is cid 10 as well. Now just hoping cricket releases Lollipop soon.....
The lollipop release for the retail (non carrier) version just came out OTA yesterday, apparently, so hopefully Cricket is not too far behind...Though it will probably take a while to go from an OTA update to a downloadable firmware image.
I contacted Motorola tech support today, they said they would replace the phone for $75 + taxes (flashing firmware via adb fastboot voids the warranty, of course), and told me it wouldn't have the Cricket firmware on it, so worst case, i would be gaining tethering ability, best case, they might send me a variant (xt1039?) that is capable of being rooted and installing a custom ROM in addition to tether. I'll probably take this option if I'm not able to get it working once the lollipop xt1045 firmware file shows up.
That's not a bad deal. Hopefully you can get it working when lollipop comes out though. Thanks for the update!

Oneplus one rebooting at boot animations!!! Please help

I have been using Oneplus one for like 1 year or so, and its a beast :good: without wasting time lets COME TO THE POINT "i have a problem":
1) it reboots continuously when at Boot animation, things i have already done>>
a)factory reset,
b)installed various other roms,:crying:
c)did unbrick technique,
d)flashed stock rom using ADB shell,
e)Erased and flashed persist.img,
F)contacted support team, they took a Remote session but all in vain,
Phew!!! but no luck
NOTE:
it reboots only when i flash Android version 5.0 or higher.
On kitkat it works fine what could be the reason, This a'int a hardware problem i guess .
Bonus query(That may help ) :
2)When i got the oneplus after flashing many roms,
I noticed it shows only 1869 MB ram while its 3 GB (should be 2556 mb or so),
and 2.5/2,7 Gb in android version 5.0 or higher,
SO PLEASE ANDROIDIANS , HELP ME!!!!!!
@adarsh58 I assume that you've unlocked ur bootloader etc. so just scroll down to step 9 and flash the file u need to go from kitkat to lollipop.
The reason why the roms are stuck on the bootanimation is because the bootloader and modem files are updated so it will only give errors and will cause an bootloop if you don't update them. Try it and report back :good:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
About your ram issue, just try to flash these files and see how it goes as the issue existed I believe when people tried kitkat again when first using lollipop roms so I guess the roms eventually caused a conflict
Thanks for the HELP!!!!
wulsic said:
@adarsh58 I assume that you've unlocked ur bootloader etc. so just scroll down to step 9 and flash the file u need to go from kitkat to lollipop.
The reason why the roms are stuck on the bootanimation is because the bootloader and modem files are updated so it will only give errors and will cause an bootloop if you don't update them. Try it and report back :good:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
About your ram issue, just try to flash these files and see how it goes as the issue existed I believe when people tried kitkat again when first using lollipop roms so I guess the roms eventually caused a conflict
Click to expand...
Click to collapse
Thanks so much for giving your time,
I will try these things as soon as i will leave my office and report back to you .
I have got OP3 too but dont want to leave my OPO like this, i cant see him dead.
Hopefully it might work
Have a nice day :good:
@adarsh58 don't worry ur OPO isn't dead, and it won't die :good:
You have a nice day too just mention me if you still have issues afterwards
@wulsic Thanks for being so generous and kind. will get back to you soon
@wulsic
Hey It dint work what can we do now ?
adarsh58 said:
@wulsic
Hey It dint work what can we do now ?
Click to expand...
Click to collapse
Well, you could try back to stock via fastboot I suppose right? Like it should flash it out of the box so nothing should go wrong, ofc download properly for 16 or 64gb and don't forget to flash any file :good:
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
If you've also tried this then I've gotta think what could be it then:silly:
wulsic said:
Well, you could try back to stock via fastboot I suppose right? Like it should flash it out of the box so nothing should go wrong, ofc download properly for 16 or 64gb and don't forget to flash any file :good:
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
If you've also tried this then I've gotta think what could be it then:silly:
Click to expand...
Click to collapse
i have done this already
I think he wont make it to be with me again ,SADLY
adarsh58 said:
i have done this already
I think he wont make it to be with me again ,SADLY
Click to expand...
Click to collapse
Ahh let me think about it :good: sorry I couldn't fix it so fast but kitkat works right?
wulsic said:
Ahh let me think about it :good: sorry I couldn't fix it so fast but kitkat works right?
Click to expand...
Click to collapse
dont b sorry!!! its a piece of Software we can not predict it , anyways thanks for helping.
and no nothing is working now .
Sday i recreated the android file system.
ls -l /dev/block/platform/<block_device_name>/by-name/
make_ext4fs dev/block/platform/msm_sdcc.1/by-name/pesist
hihihi,but all in vain :silly:
@adarsh58 still don't worry too much as it's still more likely an software issue and I know for sure if kitkat worked before it'll work again :good: I'll try to find an good answer for you today:good:
wulsic said:
@adarsh58 still don't worry too much as it's still more likely an software issue and I know for sure if kitkat worked before it'll work again :good: I'll try to find an good answer for you today:good:
Click to expand...
Click to collapse
Thanks a lot bro till then i will try to find something else :good::good::good::good::good::good::good::laugh::laugh::laugh::laugh::laugh:

Stock Bootloader

Does anyone know where I can get just the stock bootloader image to flash via TWRP?
Long story short I F'd up my bootloader and now Odin will not flash a stock BL file do to a version mismatch and to make matters worse I can't find a way to restore to stock baseband so my network isn't working. If someone can share a backup that'd be super
EDIT: Forgot to specify I need it from a TMobile variant (J700T) for firmware APK6 or APK3 (Odin doesn't seem to want to flash the stock BL from my Odin ROMs perhaps because there is a version mismatch in the phone?)
NullaVisus said:
Does anyone know where I can get just the stock bootloader image to flash via TWRP?
Long story short I F'd up my bootloader and now Odin will not flash a stock BL file do to a version mismatch and to make matters worse I can't find a way to restore to stock baseband so my network isn't working. If someone can share a backup that'd be super
EDIT: Forgot to specify I need it from a TMobile variant (J700T) for firmware APK6 or APK3 (Odin doesn't seem to want to flash the stock BL from my Odin ROMs perhaps because there is a version mismatch in the phone?)
Click to expand...
Click to collapse
download latest stock rom at sammy..
Already tried. Looks like I am officially a victim of a partial brick (Odin wont flash BL because it thinks I'm downgrading and I have no Baseband/network) I'll try and see what I can do through TWRP since I can still flash that through Download mode. I made no backups myself but would restoring another TWRP backup solve it perhaps?
NullaVisus said:
Already tried. Looks like I am officially a victim of a partial brick (Odin wont flash BL because it thinks I'm downgrading and I have no Baseband/network) I'll try and see what I can do through TWRP since I can still flash that through Download mode. I made no backups myself but would restoring another TWRP backup solve it perhaps?
Click to expand...
Click to collapse
try flash custom rom after that flash stock rom..
khaisttj92 said:
try flash custom rom after that flash stock rom..
Click to expand...
Click to collapse
No dice my dude. However, I did find something else
Turns out when I check the bootloader version it reads J700T1UVU3AQC3. Sure enough there was a baseband update and security update a few days ago and my device must've installed it while I was asleep. This would explain why my baseband is broken AND why Odin doesn't want me to flash the APK6 Bootloader.
So there's good news and bad news. The good news is there is hope but the bad news is I am currently at the mercy of whenever someone decides to upload this firmware on the internet (if anyone does that is)
NullaVisus said:
No dice my dude. However, I did find something else
Turns out when I check the bootloader version it reads J700T1UVU3AQC3. Sure enough there was a baseband update and security update a few days ago and my device must've installed it while I was asleep. This would explain why my baseband is broken AND why Odin doesn't want me to flash the APK6 Bootloader.
So there's good news and bad news. The good news is there is hope but the bad news is I am currently at the mercy of whenever someone decides to upload this firmware on the internet (if anyone does that is)
Click to expand...
Click to collapse
sorry dude i cant help u because im using f variant..
khaisttj92 said:
sorry dude i cant help u because im using f variant..
Click to expand...
Click to collapse
Thanks anyways my dude
NullaVisus said:
Thanks anyways my dude
Click to expand...
Click to collapse
your welcome..
NullaVisus said:
No dice my dude. However, I did find something else
Turns out when I check the bootloader version it reads J700T1UVU3AQC3. Sure enough there was a baseband update and security update a few days ago and my device must've installed it while I was asleep. This would explain why my baseband is broken AND why Odin doesn't want me to flash the APK6 Bootloader.
So there's good news and bad news. The good news is there is hope but the bad news is I am currently at the mercy of whenever someone decides to upload this firmware on the internet (if anyone does that is)
Click to expand...
Click to collapse
You are lucky because you at least have a functioning bootloader and a working TWRP. You are unlucky because AQC3 firmware is not available publicly yet. In any case, bootloader cannot be flashed in TWRP as far as I know. Your only option is to get your missing ACQ3 partitions from someone else's back up. IF you have messed up your EFS partition though you are out of luck.
So exactly what partitions do you need? I may be able to give you those partitions if I have a personal backup of those from the past. Right now I have modified so many things that a current copy of my partitions will probably do you more harm than good.
najoor said:
You are lucky because you at least have a functioning bootloader and a working TWRP. You are unlucky because AQC3 firmware is not available publicly yet. In any case, bootloader cannot be flashed in TWRP as far as I know. Your only option is to get your missing ACQ3 partitions from someone else's back up. IF you have messed up your EFS partition though you are out of luck.
So exactly what partitions do you need? I may be able to give you those partitions if I have a personal backup of those from the past. Right now I have modified so many things that a current copy of my partitions will probably do you more harm than good.
Click to expand...
Click to collapse
As far as I know I just need a main system.img backup
Edit; to specify, if I was flashing with Odin it would be what I would put in the AP slot
The phone in its current state is extremely slow and buggy. My intuition tells me that the older Android version does NOT like the new fiirmware (The bootloader is also where the firmware/device config info is stored IIRC)
NullaVisus said:
As far as I know I just need a main system.img backup
Edit; to specify, if I was flashing with Odin it would be what I would put in the AP slot
The phone in its current state is extremely slow and buggy. My intuition tells me that the older Android version does NOT like the new fiirmware (The bootloader is also where the firmware/device config info is stored IIRC)
Click to expand...
Click to collapse
I can give you a system image but you will have to flash it in TWRP.
najoor said:
I can give you a system image but you will have to flash it in TWRP.
Click to expand...
Click to collapse
Thats fine. I already know how
NullaVisus said:
Thats fine. I already know how
Click to expand...
Click to collapse
Well lucky me Ive got a similar situation though I reflashed with a 3-part HOME file from sammobile to unroot/unTWRP, but did so not realizing the darn BL wasnt included. Lucky for me my build versions matched, so Odin flashed flawlessly, the device boots as if it were brand new, stock recovery and all, everything functions/boots as it should, splash, factory setup, TMobile network works fine etc - only problem is both SafetyNet tests fail, so Google wont let me use use Android Pay and every other payment app that hooks into their API shuts me out. I also noticed a lightning-fast error right before going into the bootloader if you boot from the stock recovery (its so fast I need to capture the log to see what it is).
Any suggestions on where to find a BL to go with my J700T & assuming I find one, any nuances I should be aware of when flashing so as to avoid a potential brick situation?
FYI I flashed with the below from sammobile (and yes I was already at AQF1).
J700TUVS3AQF1_J700TTMB3AQF1_J700TUVS3AQF1_HOME.tar
rawkahn said:
Well lucky me Ive got a similar situation though I reflashed with a 3-part HOME file from sammobile to unroot/unTWRP, but did so not realizing the darn BL wasnt included. Lucky for me my build versions matched, so Odin flashed flawlessly, the device boots as if it were brand new, stock recovery and all, everything functions/boots as it should, splash, factory setup, TMobile network works fine etc - only problem is both SafetyNet tests fail, so Google wont let me use use Android Pay and every other payment app that hooks into their API shuts me out. I also noticed a lightning-fast error right before going into the bootloader if you boot from the stock recovery (its so fast I need to capture the log to see what it is).
Any suggestions on where to find a BL to go with my J700T & assuming I find one, any nuances I should be aware of when flashing so as to avoid a potential brick situation?
FYI I flashed with the below from sammobile (and yes I was already at AQF1).
J700TUVS3AQF1_J700TTMB3AQF1_J700TUVS3AQF1_HOME.tar
Click to expand...
Click to collapse
The bootloader is always included with the firmware and is most certainly included with the firmware you posted.
Safetynet probably fails because you need to factory reset.

I bricked my S7... can it be fixed?

So I modded the hell out of my stock rom and eventually broke it. After failing to flash the stock firmware about 50 times I gave up and put Lineage OS on my phone. Eventually I decided I wanted to try putting the stock back on and somehow screwed up my IMEI crap and don't have a backup. Basically all my phone can do is run stock rom but without any mobile network support or the same thing with Lineage OS. I've spent hours trying to fix it but nothing's worked. I checked just about every guide I've been able to find and none of them work. the issue is either not fixed or there's some kind of an error/change during the process that makes it so I can't continue. I downloaded some combination file that is supposed to help fix the issue but it won't flash via ODIN like the guide says so i can't do that.
I really need this phone up and working again. Anyone got any ideas? As of right now I have a paper weight that I can browse the internet on.
Update: I fixed it by flashing Android 8.0.0 firmware onto my phone instead of 7.0.0. I'm not sure why that fixed it because even lineage OS couldn't get my IMEI number but it's working now.
PimpWithALimp95 said:
So I modded the hell out of my stock rom and eventually broke it. After failing to flash the stock firmware about 50 times I gave up and put Lineage OS on my phone. Eventually I decided I wanted to try putting the stock back on and somehow screwed up my IMEI crap and don't have a backup. Basically all my phone can do is run stock rom but without any mobile network support or the same thing with Lineage OS. I've spent hours trying to fix it but nothing's worked. I checked just about every guide I've been able to find and none of them work. the issue is either not fixed or there's some kind of an error/change during the process that makes it so I can't continue. I downloaded some combination file that is supposed to help fix the issue but it won't flash via ODIN like the guide says so i can't do that.
I really need this phone up and working again. Anyone got any ideas? As of right now I have a paper weight that I can browse the internet on.
Update: I fixed it by flashing Android 8.0.0 firmware onto my phone instead of 7.0.0. I'm not sure why that fixed it because even lineage OS couldn't get my IMEI number but it's working now.
Click to expand...
Click to collapse
Quickest way to solve the issue as you've found out is to flash latest stock for device. Bootloader was the source of your problems, once upgraded it cannot be downgraded no matter what. All these bull sh1t guides saying you can just end up with a bricked phone.
Now BACK UP your EFS partition so this doesn't happen again.
cooltt said:
Quickest way to solve the issue as you've found out is to flash latest stock for device. Bootloader was the source of your problems, once upgraded it cannot be downgraded no matter what. All these bull sh1t guides saying you can just end up with a bricked phone.
Now BACK UP your EFS partition so this doesn't happen again.
Click to expand...
Click to collapse
I am planning on install a One UI Based rom on my S7, my phone is running stock without any rood or something like this.
How to flash the Rom without making a stupid thing that will brick my phone? i mean how to start all the process from zero?
And another thing i wonder about, what is the IMEI thing that you guys talked about?
rheh104 said:
I am planning on install a One UI Based rom on my S7, my phone is running stock without any rood or something like this.
How to flash the Rom without making a stupid thing that will brick my phone? i mean how to start all the process from zero?
And another thing i wonder about, what is the IMEI thing that you guys talked about?
Click to expand...
Click to collapse
1. Go here to download TWRP an install it via ODIN,
https://twrp.me/Devices/Samsung/
2. In TWRP select backup and choose only EFS and back it up to your external card (preferably also to your PC)
that will backup your IMEI etc
Huzaifa_Aziz said:
1. Go here to download TWRP an install it via ODIN,
https://twrp.me/Devices/Samsung/
2. In TWRP select backup and choose only EFS and back it up to your external card (preferably also to your PC)
that will backup your IMEI etc
Click to expand...
Click to collapse
EFS?
rheh104 said:
EFS?
Click to expand...
Click to collapse
Encrypted File System
rheh104 said:
EFS?
Click to expand...
Click to collapse
I think you need to go tutorial section first. And start from scratch. You won't be able to find the cotrects steps on dumb luck. Thank me later.
Huzaifa_Aziz said:
I think you need to go tutorial section first. And start from scratch. You won't be able to find the cotrects steps on dumb luck. Thank me later.
Click to expand...
Click to collapse
Send me a link to it please, thanks!
rheh104 said:
Send me a link to it please, thanks!
Click to expand...
Click to collapse
You have Exynos or Qualcomm variant?
I would suggest you start off from here
[LINK]https://forum.xda-developers.com/galaxy-s7/help/help-thread-question-noob-friendly-t3341138[/LINK]
rheh104 said:
Send me a link to it please, thanks!
Click to expand...
Click to collapse
I hope you have read about ODIN and FLASHING recovery by now,
https://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770 go here and flash the TWRP RECOVERY and then install any custom ROM. or
Get original Firmware from Sammobile.com and Flash it via ODIN

Categories

Resources