Related
Just bought a TF700 from Amazon (much cheaper in the States than where i live) but got a few questions:
(a) Its still on ICS and I suspect that i will end up installing custom roms etc as I have done with my GS2. I read that i should before i root or unlock bootloder i should backup using NVflash (i think mine is pre 30) but does that prevent me from going to JB or does it not matter?
(b) I use wifi channel 13 at home, but i know my tablet as i bought in US probably has wifi channels 1 to 11. How can i change the wifi to include up to channel 13?
(c) Are there any other diff between a US version of TF700 and a WW version? I note that on the Asus website they have different firmwares.
Thanks!
blion said:
Just bought a TF700 from Amazon (much cheaper in the States than where i live) but got a few questions.
Are there any other diff between a US version of TF700 and a WW version? I note that on the Asus website they have different firmwares.
Thanks!
Click to expand...
Click to collapse
It is possible to convert your tab to the World Wide or other appropriate firmware by a reflash.
Do you know how this is accomplished?
If not post back and we can guide you.
Also I'm not sure about the wifi channel change, yet there there is most likely a way to change that.
The way to change the WiFi is via a build.prop text edit hack. It's as simple as changing the country code from US to GB
You must be at least rooted to do it. Of course if you take an nvflash blob copy then unlock the world is your oyster! :victory:
Thats OK said:
It is possible to convert your tab to the World Wide or other appropriate firmware by a reflash.
Do you know how this is accomplished?
If not post back and we can guide you.
Also I'm not sure about the wifi channel change, yet there there is most likely a way to change that.
Click to expand...
Click to collapse
Sorry but I dont know how to convert it to a WW. Would appreciate it if you could let me know!
Do you know what are the difference between a US and WW firmware other than the Wifi channel??
Also do you know the answer to my question (a)? I want to update to JB but worried i wont be able to after using NVflash.....
sbdags said:
The way to change the WiFi is via a build.prop text edit hack. It's as simple as changing the country code from US to GB
You must be at least rooted to do it. Of course if you take an nvflash blob copy then unlock the world is your oyster! :victory:
Click to expand...
Click to collapse
Thanks but could you provide more info on how to edit build.prop??
I will try and root tonight. Can you explain what is an nvflash blob copy??? I come from using GS2 where there was not a need to unlock the bootloader but i read that unlocking the bootloader (and therefore losing warranty) is required in order to install a custom rom.
blion said:
Thanks but could you provide more info on how to edit build.prop??
I will try and root tonight. Can you explain what is an nvflash blob copy??? I come from using GS2 where there was not a need to unlock the bootloader but i read that unlocking the bootloader (and therefore losing warranty) is required in order to install a custom rom.
Click to expand...
Click to collapse
Doing the nvflash thing will in no way stop you updating to jellybean however updating to jellybean will stop you doing the nvflash thing. Nvfash is security nothing more. You can recover from any bricks after you do it.
As for gaining root and editing build.prop I would suggest you read the stickies in the general forum. Think about unlocking and flashing a custom rom if you are not comfortable doing the edits yourself as it's all too easy to get into a bootloop (recoverable) if you don't know what you are doing.
Do you know what are the difference between a US and WW firmware other than the Wifi channel??
Hi, I have a tf700 that I bought from the US and I live in the UK, I have always used US firmware and have never had a problem with wifi.
maxal said:
Do you know what are the difference between a US and WW firmware other than the Wifi channel??
Hi, I have a tf700 that I bought from the US and I live in the UK, I have always used US firmware and have never had a problem with wifi.
Click to expand...
Click to collapse
You won't but if you set your UK wifi router to use channel 13 you will Your US infinity won' see it. To fix you flash a WW rom or do the build prop edit and it will work again.
As for other differences I'm yet to find any yet. Other than wifi they both behave the same way.
maxal said:
Do you know what are the difference between a US and WW firmware other than the Wifi channel??
Click to expand...
Click to collapse
AFAIK, the list of included system apps is slightly different, and also the other apps are at least recompiled for each country version.
Good news......confirmed my new tab is 9.4.5.26 version which i think will enable me to use NVflash!!
I want to try Cleanrom and want to make sure i get this absolutely correct (i dun wanna brick my new tf700!!!).
(a) Follow the guide to backup using NVflash (http://androidroot.mobi/t3_nvflash/)
(b) Install the official asus 4.1.1 bootloader (current version seems to be V10.4.4.23)
(c) Install TWRP 2.3.1.0 (follow this guide http://forum.xda-developers.com/showthread.php?t=1938129)
(d) Do i still need to install SuperSU or can I go to install Cleanrom directly??
Is there anything i should be mindful of before flashing??
Thanks in advance!!!!
blion said:
Good news......confirmed my new tab is 9.4.5.26 version which i think will enable me to use NVflash!!
I want to try Cleanrom and want to make sure i get this absolutely correct (i dun wanna brick my new tf700!!!).
(a) Follow the guide to backup using NVflash (http://androidroot.mobi/t3_nvflash/)
(b) Install the official asus 4.1.1 bootloader (current version seems to be V10.4.4.23)
(c) Install TWRP 2.3.1.0 (follow this guide http://forum.xda-developers.com/showthread.php?t=1938129)
(d) Do i still need to install SuperSU or can I go to install Cleanrom directly??
Is there anything i should be mindful of before flashing??
Thanks in advance!!!!
Click to expand...
Click to collapse
You'll need to unlock it at some point too
SuperSu is included in CleanROM so not needed.
It's all very straight forward and remember because you are coming from Stock you won't need to do a full wipe.
sbdags said:
You'll need to unlock it at some point too
SuperSu is included in CleanROM so not needed.
It's all very straight forward and remember because you are coming from Stock you won't need to do a full wipe.
Click to expand...
Click to collapse
Thanks! Ops forgot about unlock. Will unlock, backup NVflash, install asus bootloader, TWRP and then insall cleanrom???
Lastly, should i install odex or deodex version of cleanrom??? The verdict seems to be split.....not sure what practical difference there is between the two..............
blion said:
Thanks! Ops forgot about unlock. Will unlock, backup NVflash, install asus bootloader, TWRP and then insall cleanrom???
Lastly, should i install odex or deodex version of cleanrom??? The verdict seems to be split.....not sure what practical difference there is between the two..............
Click to expand...
Click to collapse
I'd start with the deodex version but they are so close to each other and easy to switch between. Try them both. You don't lose any apps or data by switching between the two as same base.
Hello, I own a TF300TG which mounts 4.2.1 android version, 10.6.2.11 fw.
I'm trying to root it with SRS root (eset32 detected it as trojan, btw) but it keeps failing.
VROOT doesn't even install on my PC (i don't know why, it's written in chinese).
how can I obtain root privileges?
xperiaL said:
Hello, I own a TF300TG which mounts 4.2.1 android version, 10.6.2.11 fw.
I'm trying to root it with SRS root (eset32 detected it as trojan, btw) but it keeps failing.
VROOT doesn't even install on my PC (i don't know why, it's written in chinese).
how can I obtain root privileges?
Click to expand...
Click to collapse
The easiest way is to unlock your bootloader, install a custom recovery like TWRP and then flash the SuperSU ZIP from that recovery.
Make sure you double-check that you picked the right recovery version for your bootloader.
Sent from my TF300T using Tapatalk
I've found some threads linking to twrp but the link shared in them refer to the tf300t, not tg. I mean this. Is it the same? I'm worried about bricking my device, because it isn't only mine
so where can I get the correct files to download for my tablet?
sorry if Iook like a noob but my phone was waaaaaayyyy easier to root...
xperiaL said:
I've found some threads linking to twrp but the link shared in them refer to the tf300t, not tg. I mean this. Is it the same? I'm worried about bricking my device, because it isn't only mine
so where can I get the correct files to download for my tablet?
sorry if Iook like a noob but my phone was waaaaaayyyy easier to root...
Click to expand...
Click to collapse
Yeah, it is tricky to pick the right recovery version with all those incompatible bootloaders and the new KitKat ROMs needing yet another one to flash properly.
There are other options for rooting, search for motochopper and similar tools, but personally I don't regard them as simple and some of them have been reported to contain malware.
To help you find the right recovery version, first need to know the version of your bootloader. You can find it at the top left of the bootloader screen. The interesting part are the numbers starting with 10. or 9. for really old ones. Then need to know, what ROM you want to root. Using stock Asus ROM?
You can safely use a recovery for TF300T; it is much more important to pick the right version for your bootloader.
Sent from my TF300T using Tapatalk
I've found this guide (-> http://forum.xda-developers.com/showthread.php?t=2617298) which seems pretty good, but the version reported working is WW_epad-10.6.2.10, while mine is 10.6.2.11-20131213
what do you suggest me to do? Go ahead and try it or hope one day a more specific version will be released?
xperiaL said:
I've found this guide (-> http://forum.xda-developers.com/showthread.php?t=2617298) which seems pretty good, but the version reported working is WW_epad-10.6.2.10, while mine is 10.6.2.11-20131213
what do you suggest me to do? Go ahead and try it or hope one day a more specific version will be released?
Click to expand...
Click to collapse
The guide looks good to me and should work fine for your boot loader.
Instead of the attached TWRP, you can safely use any TWRP for the TF300T, as long as it has -42 in the name. 2.6.0.0 might be a little buggy, not sure.
Sent from my TF300T using Tapatalk
xperiaL said:
I've found some threads linking to twrp but the link shared in them refer to the tf300t, not tg. I mean this. Is it the same? I'm worried about bricking my device, because it isn't only mine
so where can I get the correct files to download for my tablet?
sorry if Iook like a noob but my phone was waaaaaayyyy easier to root...
Click to expand...
Click to collapse
Just to confirm that i have TF300TG with JB 4.2.1 and my bootloader is 10.6.2.11 and i have used the link that you quoted in this reply (this) and all work for me just fine.:good:
Kingo (google it) apparently works. so if you dont want to unlock the bootloader and whatnot, try that.
thanks for your answers, first I will try kingo and if it doesn't work I will try the method on the link I posted!
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!
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.
Hello everyone, I desperately need assistance because I think I may have soft bricked my work provided SM-A536B/DS.
What I tried to do initially is to install TWRP so I unlocked the bootloader successfully. Then, I saw different posts here on XDA where people have successfully installed cust ROMs so i tried to do that. This is when the problems started...
Right now my phone is bricked, I assume it is a soft brick because I can still get it to download mode. I did some research prior writing here, and everyone is mentioning to flash the stock ROM. That does not work.
Right now, the phone has bootloader unlocked: (Screen1)
It is asking me to lock it, so that means it's already unlocked.
Tried to access TWRP but I cannot since I get this screen when I do vol up + power: (Screen 2)
My phone was bought in Europe. I am not entirely sure whick ROM is the right one. Is there a way to check which is the right one to download? There are multiple ROMs I can download for Europe: (Screen3)
My country is not in the list so i downloaded the 2 generic for Europe. I put my phone in download mode: (Screen4)
However Odin fails everytime, no matter what files I add: (Screen5), (Screen6)
Since TWRP is not working, I locked the bootloader again to see if I could get Samsung bootloader to show up. I think i might have deleted it somehow, because I get the same thing as before when i do vol up + power. And as you can see, the bootloader is not locked: (Screen7)
I am now stuck and screwed, because this is my work phone. Any help is greatly appreciated.
psorincatalin87 said:
Hello everyone, I desperately need assistance because I think I may have soft bricked my work provided SM-A536B/DS.
What I tried to do initially is to install TWRP so I unlocked the bootloader successfully. Then, I saw different posts here on XDA where people have successfully installed cust ROMs so i tried to do that. This is when the problems started...
Right now my phone is bricked, I assume it is a soft brick because I can still get it to download mode. I did some research prior writing here, and everyone is mentioning to flash the stock ROM. That does not work.
Right now, the phone has bootloader unlocked: (Screen1)
It is asking me to lock it, so that means it's already unlocked.
Tried to access TWRP but I cannot since I get this screen when I do vol up + power: (Screen 2)
My phone was bought in Europe. I am not entirely sure whick ROM is the right one. Is there a way to check which is the right one to download? There are multiple ROMs I can download for Europe: (Screen3)
My country is not in the list so i downloaded the 2 generic for Europe. I put my phone in download mode: (Screen4)
However Odin fails everytime, no matter what files I add: (Screen5), (Screen6)
Since TWRP is not working, I locked the bootloader again to see if I could get Samsung bootloader to show up. I think i might have deleted it somehow, because I get the same thing as before when i do vol up + power. And as you can see, the bootloader is not locked: (Screen7)
I am now stuck and screwed, because this is my work phone. Any help is greatly appreciated.
Click to expand...
Click to collapse
This is why it's a bad idea to screw with work provided devices. You don't own the phone, and you will be held financially responsible for it if it's damaged or broken.
You're trying to flash the wrong firmware. You have G925F selected; your device is an A536B. The latest firmware for your device is A536BXXU4BVL2. Use Frija to download the latest firmware.
Since this is a work owned device, the only advice I will offer is this: Return the phone to stock with the correct software, re-lock the bootloader, and do not attempt to modify it as it is most likely in violation of your company's technology acceptable use policy.
V0latyle said:
This is why it's a bad idea to screw with work provided devices. You don't own the phone, and you will be held financially responsible for it if it's damaged or broken.
You're trying to flash the wrong firmware. You have G925F selected; your device is an A536B. The latest firmware for your device is A536BXXU4BVL2. Use Frija to download the latest firmware.
Since this is a work owned device, the only advice I will offer is this: Return the phone to stock with the correct software, re-lock the bootloader, and do not attempt to modify it as it is most likely in violation of your company's technology acceptable use policy.
Click to expand...
Click to collapse
Yes, this is what I am trying to do, to return to stock ROM. I downloaded A536BXXU4BVL2 for my phone, not G925F (this is what Odin uses as an example).
psorincatalin87 said:
Yes, this is what I am trying to do, to return to stock ROM. I downloaded A536BXXU4BVL2 for my phone, not G925F (this is what Odin uses as an example).
Click to expand...
Click to collapse
What version of Odin are you using?
Your bootloader is still unlocked, correct?
If you're unable to reflash the OEM firmware in Odin, I don't think there's anything else that can be done.
To be completely honest with you, I'm not sure trying to help you is worth the effort, because you did something you shouldn't be doing anyway, and any consequences you may face are entirely of your own doing.
V0latyle said:
What version of Odin are you using?
Your bootloader is still unlocked, correct?
If you're unable to reflash the OEM firmware in Odin, I don't think there's anything else that can be done.
To be completely honest with you, I'm not sure trying to help you is worth the effort, because you did something you shouldn't be doing anyway, and any consequences you may face are entirely of your own doing.
Click to expand...
Click to collapse
Yes, i know I did something bad and I learned my lesson.
I'm using Odin 3.14 and indeed, bootloader is still unlocked. I really appreciate the help!
psorincatalin87 said:
Yes, i know I did something bad and I learned my lesson.
I'm using Odin 3.14 and indeed, bootloader is still unlocked. I really appreciate the help!
Click to expand...
Click to collapse
I downloaded the firmware with Frija and I get the same issue with Odin.
psorincatalin87 said:
I downloaded the firmware with Frija and I get the same issue with Odin.
Click to expand...
Click to collapse
What options do you have checked in Odin?
V0latyle said:
What options do you have checked in Odin?
Click to expand...
Click to collapse
I haven't touched any of the options, everything is on default.
While reading this post something popped in my head.
I dont have this phone, but a Xiaomi Mi8.
When I want to adb push or sideload stuff into phone while it is in recovery or download mode, certain usb ports will work and others wont. And there is not a clear error when it's plugged to non-working usb port, just fails in the middle of a transfer with a generic error message.
Maybe totally irrelevant, just wanted to share.
nsfnd said:
While reading this post something popped in my head.
I dont have this phone, but a Xiaomi Mi8.
When I want to adb push or sideload stuff into phone while it is in recovery or download mode, certain usb ports will work and others wont. And there is not a clear error when it's plugged to non-working usb port, just fails in the middle of a transfer with a generic error message.
Maybe totally irrelevant, just wanted to share.
Click to expand...
Click to collapse
OH.MY.GOD! Thank you very much, man! I love you! I could kiss you right now, stranger!
Haha I'm glad it worked.
Hope you get better luck on your future rom adventures.
nsfnd said:
Haha I'm glad it worked.
Hope you get better luck on your future rom adventures.
Click to expand...
Click to collapse
Nah, this is my last one.
psorincatalin87 said:
Nah, this is my last one.
Click to expand...
Click to collapse
don't be that way lol, it's fun, just do it on hardware you own. get a cheap phone off ebay to play with