So, Im a contractor. Field Services mostly. Break/Fix and Installs for POS mostly.
Anyway, a recent contract I picked up found me installing new, cheap music solutions for a chain of gas stations im sure you've heard of. Regardless, the tab 8's they were using prior are old enough that they didn't want them back. I figured, well, it's a chance to break stuff potentially, and proceeded to do just that, unintentionally really.
Problem is, my dumbass jumped the gun and didn't really know much about MDM and wiped the cache before having the idea of calling my Buyer, and asking them to remove it from their MDM lineup. They did so, but it's essentially too late to matter now. Tablet just boots to the Sprint Logo and never goes past it. Odd, considering nothing ever sucessfully flashed the darn thing, but it's doing it nonetheless. I've tried MANY versions of Odin trying to flash TWRP but it always says MDM Mode: Cant Download on the tablet. It's safe to assume i've done everything youre not supposed to do in banging my head against the wall with this thing.
I've searched the forums over and over again, downloaded so many firmwares that I'd not be surprised if the internet held no more options than the ones I've gotten. Why would I need the firmware if TWRP never flashed? Because I've tried damn near everything I think. Including Heimdall. Im on a dual boot machine, and would prefer a Linux based solution if there is one to be had, but can go for Windows also I suppose.
What else...ADB and Fastboot both never detect the tablet, but I can lsusb and see the device, which mode it's in ( usually Download Mode, but also shows up as MTP if I am in Recovery ), and the bus info. If I go to recovery, and use update via ADB, obviously, ADB sees the device then, and I can sideload, but nothing works so far. It' always gives me a Error 21: Footer is Wrong no matter what I try to sideload.
Odin I do not remember what error it gave specifically, I'll try to hunt up a log somewhere, but I know when trying to flash the TWRP it would say something about write protection I think maybe? Not entirely sure. When just trying to flash the firmware, it would go past aboot.mbn to the next file and then fail, every single time.
Any help would be greatly appreciated. It's a cheap little paperweight, but it's a learning experience.
Nobody? Although I am not surprised, I am a bit disheartened. Mostly because it really is a learning experience really. It's difficult to express what my mind is trying to learn at any given time let alone search for an answer, being the worst case of ADD i've ever seen. Heh.
I've noticed that I can successfully flash some files, but not most others, and flashing said files seems to make no difference, probably because boot.img nor recovery.img are among the files that will successfully flash via sideload. Aboot.mbn, and Modem.bin both flashed I believe, and by that I mean, flash without giving me some sort of error such as failed to unpack lack packet or some such.
Trying to magic out how the damned things works hasn't gone great either. I"ve discovered the magical linux tool binwalk which is great, but either limited by what it can do, or im just too uneducated in it's proper usage despite reading the man over and over again....mostly.
Strangest thing...extracting the files examined with binwalk sometimes produces many magnitudes of size bigger files than the file contained. I am not exaggerating either. Extract a 1GB file and it produces less than that initially, then extract those files and I swear to God I get somewhere like 40GB, which is impossible as far as I"ve ever seen.
Related
So, I was at work today, and a customer came and asked if I can recover her deleted picture on her GS4 I337. I thought, OK, I've never played with S4, this is a good chance. So I took the phone and started mess around with it.
As Usual, before any recovery, you need to do a 1:1 backup of the device. so I was thinking, android's file system is basically ext4, if I could install a busybox, I can then make a clone of the internal storage with dd or whatever; before I can install busybox, I need to root the phone.
so without carefully reading I just downloaded kingo android root I found in GS4 forum. and it worked out pretty well.
then, maybe because I haven't had any breakfast, or something....my mind wasn't thinking stuff right.....I told myself that I need to find a busybox flashable and flash it into the phone. so I found the busybox flashable zip. but for obvious reason the stock recovery didn't take it lol. at that point I was like, ok let's try something else....because I need a custom recovery to flash anything other than stock auth ....
and I found CASUAL....again, without reading the manual, I just plugged in the phone and clicked go...
after CASUAL finished its job, it reboot the phone, and I found myself in deep****.....
the phone is stocked in download/odin mode.....
I was scared ****less...after search and read like a crazy, I found out that 1, there's no custom recovery for MF3 and, 2, CASUAL doesn't work for MF3 phones (before soft-brick I don't even know what's MF3 lol)...and, 3, people with similar issue sent their phone over to a ebay seller who offers jtag unbricking service for $30...
after reading CASUAL log, I noticed that CASUAL didn't successfully flash the recovery(of course) but it just went ahead with the progress anyways...so, I think there's something wrong with the boot env or bootstrap it mess up to cause the phone not able to boot up.
so I thought, if I can find the stock rom and flash boot.img, maybe it will unbrick the phone.
because it was a HUGE responsibility, it's not my own phone. it's a customer's, and may or may not contain life and death information in there that was probably why the owner was willing to pay for recovery service at the first place... and I mess it up for her...it was so much pressure.....
thank god it was not the end of my life....
I downloaded and extracted I337UCUAMDL_I337ATTAMDL_ATT.zip, and tried to flash the boot.img with Heimdall .
heimdall flash --BOOT boot.img
heimdall failed with a message like "there's no partition name boot" or something, BUT it DID successfully update the PIT, and rebooted the phone. Magically, the phone came back alive. PIT corrected the partition problem so phone will boot normally??? I was SO HAPPY!!!!
I stopped there and put the phone aside, I don't wanna touch it anymore LOL
I actually posted a small guide about how to get it back up and working again, but you nuked her recovery. She'll have to get it fixed at a Samsung experience shop. They do it for free.
Sent from my SAMSUNG-SM-N900A using Tapatalk 5
If only I found your guide at my 3-hour panichour lol
I am not sure if the stock recovery is still there. do you think technically I can use heimdall flash --RECOVERY recovery.img to reflash the recovery if it was nuked?
crumpz said:
If only I found your guide at my 3-hour panichour lol
I am not sure if the stock recovery is still there. do you think technically I can use heimdall flash --RECOVERY recovery.img to reflash the recovery if it was nuked?
Click to expand...
Click to collapse
It's been posted in many threads about manually putting the phone into ODIN (download) mode and then manually cancelling out to usually boot the phone. However, as mentioned, the stock recovery probably no longer works. It seems to me, and you mentioned it a couple of times yourself that your biggest issue is not reading about what it is you are doing. Hopefully, you learned a lesson about that.
Hey all,
Long story short. I made a backup copy of my build.prop to my internal SD. I edited one line in the /system/build.prop. I rebooted. It was fine. I decided the change I made to build.prop was not necessary so I copied the backup I had on my SDCard of the original file back to /system/. My phone hangs on the "Samsung GALAXY S5 powered by Android" screen during boot.
I'm not experienced with ADB but I am technically inclined so please point out if I'm doing something wrong. I have installed the universal ADB drivers on my computer. I have installed the "Samsung USB drivers". I boot into recovery. I go to "apply update from ADB" (not sure if that is correct). I then run the command "adb devices" in Windows and it lists my device with "sideload" next to it.
I then run "adb pull /system/build.prop" and I get "error: closed". That is as far as I can get.
Any help is greatly appreciated.
taboo_ said:
Hey all,
Long story short. I made a backup copy of my build.prop to my internal SD. I edited one line in the /system/build.prop. I rebooted. It was fine. I decided the change I made to build.prop was not necessary so I copied the backup I had on my SDCard of the original file back to /system/. My phone hangs on the "Samsung GALAXY S5 powered by Android" screen during boot.
I'm not experienced with ADB but I am technically inclined so please point out if I'm doing something wrong. I have installed the universal ADB drivers on my computer. I have installed the "Samsung USB drivers". I boot into recovery. I go to "apply update from ADB" (not sure if that is correct). I then run the command "adb devices" in Windows and it lists my device with "sideload" next to it.
I then run "adb pull /system/build.prop" and I get "error: closed". That is as far as I can get.
Any help is greatly appreciated.
Click to expand...
Click to collapse
I would flash a stock rom to get the phone running again, and next time make a nandroid backup that you can restore with a custom recovery before you mess with system files.
I'm currently downloading a stock rom from a very slow source. In the 3hrs or so it's going to take to download I thought I would absolutely confirm I was buggered as it would be nice if a few ADB commands could save me.
gee2012 said:
next time make a nandroid backup with a custom recovery before you mess with system files.
Click to expand...
Click to collapse
I do certainly know better. But Samsung in their power have decided to Knox flag your device if you install a custom recovery. As such creating a nandroid backup was not an option for as long as I want my warranty. I do have Titanium backups, and I thought I was doing the right thing by making a copy of build.prop before doing anything... turns out I was wrong. But really, thanks for your concern and advice.
..
fffft said:
Three hours huh? You should talk to Santa about a faster net connection.
Click to expand...
Click to collapse
I live in Australia. We asked our government and they said yes.... then we got a new government. But in this case it's the speed of the host that was hindering. It's all elementary now anyway as the download finished. No one had replied. I flashed it. It failed. And the long and short of it is adb is now useless to me.
fffft said:
You should know this already though as a five minute search on how to use ADB would have pulled up numerous tutorials.
Click to expand...
Click to collapse
I appreciate the help. But I'd spent all day reading tutorials. Trying commands. Failing. Googling the error. Trying new commands. Failing. Googling those errors. After doing that for some time I thought it would just be more sensible to ask people that have actually had experience.
fffft said:
You're also on the wrong site if you are obsessing over the Knox flag. Yeah, it might affect your warranty. Probably not, but I'll grant that it could. So simply decide up front it you want to modify your phone or wait out your risk free warranty period.
Click to expand...
Click to collapse
So here's the thing. I don't want my cake and eat it. I will absolutely be blowing away knox. I just didn't see a point in doing it preemptively. The phone is only a couple weeks old so I decide it would be wise to at least keep my warranty until I'm happy it's rock solid and I have a good reason to lose it - nice stable Cyanogenmod I'm looking at you. Plus anything I wanted to do up to now I was able to with Towelroot and xposed. I just couldn't Nandroid.
Really. Thanks for listing the commands. As of this morning I hadn't needed to use ADB at all. I appreciate you spelling it out. I just wish I had of seen it mere minutes earlier as I would have been able to let you know if it worked. Unfortunately I didn't. But I appreciate the effort.
..
fffft said:
And you say that your firmware download speed was host limited. I just did a search for half a dozen S5 firmware builds. Found all of them widely disseminated. And as one might expect, not all of the hosts were slow..
Click to expand...
Click to collapse
I was using sammobile.com on a free account. I'm sure I could have found a faster host but I've used sammobile.com many times in the past and they've always been reliable. I'd rather wait longer and get something I trust when I'm not in a hurry than download a file that has the right name but is just from a random "megaupload" link or something.
Now regarding adb I got a lot of the information I needed through google searches. I also watched a number of videos. But here's the thing. If I were just taking the opportunity to learn about adb google-ing around would have been fine. But as the circumstances were a little dire in this situation and I've expressed that I've never used adb before and was not confident. I didn't know what I was doing or have the experience to know the implications of what I was doing. As such 1) I didn't want to take the chances of getting it wrong and screwing myself over further and 2) I seemed to have a fairly unique issue (can't boot, stock recovery, "error: close" issue).
It wasn't just about knowing the commands to use, it was about finding out whether I was even able to do what I was hoping to do from a stock recovery on an S5 (hence the title of the thread).
You're getting a little judgey, which is fine you're entitled to your opinions. But I'd ask you read my title and first post again. It wasn't about just getting the commands outright coz I was too lazy to look, it was about getting a number of questions that I didn't know the answer to due to lack of experience, and that I hadn't had directly answered through google searches. Also I never implied an urgency, it was simply a case of "I had a contingency plan in place (downloading a stock rom) but I thought I may as well ask for some advice in the time I had while waiting for it to download".
It's not as though my case was a dime-a-dozen, "answered directly a million times". It was a little more unique and I had answered many of the general questions myself and decided that my remaining hesitations are best answered by those with experience. I'm sorry that bothers you.
Plus the reason you were able to have so much success is because you have experience and knew what to look for and understood the compounding factors. I had figured your first and third command out for myself. I was missing your second and I don't know if that was my problem, but the error I was getting "error: closed" seems to have a massive lack of documentation on the internet. Not many people are talking about it and those that are pretty much just say "update abd" - I was running the latest version. That is where I was coming undone.
But if you're STILL feeling disconcerted at my efforts here is my session from yesterday right before I made this thread. This is literally only a few of the tabs I had gone through: http://i.imgur.com/WDB3qIg.png
..
I just can not understand why you're being like this man. I've been nothing but polite. But I came on here to learn. If I was doing something blatantly against the community I'd expect to hear about it, but I just wanted help. You gave me help which was awesome but every time I took it or added something to explain my reasoning for my actions you added a lecture with it.
All I was trying to put across to you was that you don't know what I did or my reasoning for asking questions. I was just hoping you could see that your initial assumption about my laziness may not have been correct. Again, I'm not trying to be a **** about this and I really was thankful for the help you gave. But it seems you're more than willing to dish out the criticism but as soon as I defend myself or talk back you in turn get your back up. But I just don't understand why you seemed so interested in making assumptions about my efforts, my internet speeds and then telling me how I should be doing everything differently.
Hi y'all, i recently within the last month 2 months taken up a very unsual craving for delving deeper into my technology, with that being said. my tab 4 7.0 sm-t230 i Downloaded an app called "lucky patcher" was messing with it, been reading about deoxe(ing) my tablet,it gave me the option to do it for me (usually i enjoy the challange of using a emulated terminal and what not) but every file etc would take too long, and it worked, my daughter ot well over 150 million score on subway surfers etc. i notice my phone sluggish even bein over clocked, I/Os that i did myself, running max cpu and performance i could blabber forever since my 3 kids arnt interested in my newly found hobbie and my husbands a truck driver, i'm getting it out here (i'm sorry but i do need help) so anywyas i decided to kick her into recovery and begin to just manually delete all the dex copied files through TWRP went good till i wetn to reboot after staring at my screen for 3 hours and got threw up on twice from sick babies and i was boot looped. i decide to restore a previous freshly flashed rom/root backup. well they were deleted too. and all i could do was a master re format i think is what i read it was called, and excited to get back and re download everything i notice i now have no OS and no recoveries and TWRP fulll of emptiness. i can play through TWRP i've changed file permissions i've tried everything ive read and tried everything i learned and experianced to fix this issue, and yet stillno idea how to fix this issue..
Now the fun part is my set up. the only pc i have means and access too is my samsung Chromebook, and my tablet, that's it, no phone because my tablet handles everything my little heart can desire.
needless to say, i need some kinda recovery tool kit i can use via my chromebook, that'll allow me to use ADB for chrome (which another question i have is how do i enable my tablets USB debugging if i can't get into the phone?) so toolkit for chromebook for a ADB side load if possible. or some way to do it through my emulated terminal in TWRP,. my minds rushing, i'm confused and my over emotionally stressed female head is killing me without my tablet. (drive to any town where i could use anything but my chrome book. 3.5 hours.
sorry i pray this post doesnt get deleted. I need help because my tablet is my main source of income being in real estate when i'm back in town once a month. never made a page or a forum or anything like this usally google magic does it. but 3 days and countless mind numbing forums i've given in.. please help me! i'll donate pay something idc at this point. -a pissed off irish southen woman on the verge of pms and a meltdown thanks in advance i'll try to reply as fast as humanly possible, ill be up for awhile tonight going through more posts.
0well with a little more tinking around, i think i have found the issue as too why no matter what i do i'm unable to boot a rom/os. mt EXT3 wil not mount my system i'm clueless as to how to fix that at all threw TWRP, anyone have an idea of any kind please? i'm for anything, even if after more attempts and countless hours, i'll record me skipping it across my lake, and we'll all take guesses as too how many skips it'll do. hopefully my dog will fetch it if i throw at the wrong angle. (completely dumb jokes are the only thing keeping me from returning Sain.) we all cant be too serious. please very interested on how to fix this issue tho.
s,
you need to get a custom rom zip onto an sdcard, check development section.
in twrp, flash the rom,
if the rom still doesn't boot, then reboot to twrp again and use the format data option, then reflash rom and try again.
twrp terminal sucks, you can try flashing aromafm https://www.androidfilehost.com/?fid=95916177934547314
this is for the marvell variant, it may work for the msm/qcom variant.
stop using lucky patcher.
m
moonbutt74 said:
s,
you need to get a custom rom zip onto an sdcard, check development section.
in twrp, flash the rom,
if the rom still doesn't boot, then reboot to twrp again and use the format data option, then reflash rom and try again.
twrp terminal sucks, you can try flashing aromafm https://www.androidfilehost.com/?fid=95916177934547314
this is for the marvell variant, it may work for the msm/qcom variant.
stop using lucky patcher.
m
Click to expand...
Click to collapse
Hi, that's where another problem lies within, I have no way of communicating with the phone or being able to do much, considering the only pc/laptop i have access too is my chromebook, and this thing is a ssteaming pile of regurgitated dog bile. if theres one regret in life.. buying this thing.. even dual booted i still can't process the zips or compile them properly, maybe i need to find out how to build a zip file from scratch and comepile the corresponding stuff myself in small hopes it'll work on this chromebook
and yes, never again will I use that. it worked don't get me wrong. but then it decided to deodex my system to oblivion.
s,
hey that rhymed !
your alternative is to use a usb thumbdrive and an otg cable , else nada.
m
moonbutt74 said:
s,
hey that rhymed !
your alternative is to use a usb thumbdrive and an otg cable , else nada.
m
Click to expand...
Click to collapse
I'm gla you have a sense of humor, thank you hun. looks like i'm tabletless until i go back into town in two weeks ): i suppose till then i will tinker with it some more and unlock the universe, or find a way to convert zips that are made for windows or mac and be able to convert it to be able to be used and transfered unto the phone. Chromium os or chrome now has ADB for chrome as an extension but very iffy, has 3 options to screen record/screenshot and terminal. i was able to use vitural box for about 2 hours and force odin to pretend i was on a widnows enough to orignally root, then it crashed my chromebook. Maybe i've gotta achieve 88 mph first to get this thing to work? lol my chromebook "overclocked" 810 mghz.... maxx.... frequency says it can go to 2100... i think if i even try that i'd recreate the "hydrogen bomb"
Hello! So this may be a long post, but I don't give a heck. Also, when I say hackers, I mean In a good way, like white hats. So, here is my first inquiry. How do people even find these exploits to put in the root binary? I've read articals about people intentionally crashing devices, which then puts it in a state vulnerable enough to bruteforce the binary in (At least that's what I thought...) I know that android is also based off of java, (Once again, an assumption) and I wonder where and how people get these ideas.
My second question is, As I haven't been able to find anything of this, aren't apps installed into portions of a phone where the normal user isnt able to touch on phones without root? Again, a newbie assumption.
So anyways, I am pretty interested in android development and rooting/custom code/bootloaders, and I'm not to keen on the subject.
I am also pretty bad at understand android right now, sooo, you can laugh at me if you want :silly:
Also I don't know if this is in the right thread
Alright, so I'm not sure about this, but I was thinking about what happened yesterday, and I thought about when I accidentally flashed the wrong CP file in Odin, and then when I tried to boot it, it gave me the "An error has occurred whilst the phone was updating. Please launch the Verizon Software Assistant". I also realized very quickly, that this is just the download screen without the extra information in the top right, and also realized that the download bar shows up also when you use Odin.
To give you my real question, I want to know if the Software Assistant uses any other method that isn't using Odin, and that if that is so, If you could maybe modify where it gets the flashing files to flash files onto the phone, without the phone realizing that they aren't official files?
To also be honest, I'm not an exploit finder, and maybe other people have thought of this, but eh, why not try and ask people about it? :good:
also I don't know if the phone itself will check those files....
also here is the zip with the Software Assistant.
Click here for the Assistant.
Hi. I am not an experienced rooter, but I managed tp root my Samsung Note3 a few years ago using Odin and some files I found here on the XDA site. I haven't used it for a couple of years.
I now need a second phone purely for work and wonder if the phone is safe enough to use today. I keep hearing things about newer phones and security updates, and am fearful of using the phone in case it is unsafe in some way.
Also, I have deleted some programs the playing with it, and don't know if I have messed it up.
Can I flash the phone again, and will a new file reinstall the whole operating system?
I don't mind buying a new phone if I have to, but love the idea of making the phone do what I want it to do rather than being told how it can be used by the manufacturer. The trouble is, I'm not an expert, and am unsure what I am doing. I love the Note3 and would love to feel safe enough to use it with an email account without the fear of my data being stolen by hackers.
Any thoughts would be gratefully received, thanks.
) Can I flash the phone again, and will a new file reinstall the whole operating system? )
Yes flash latest stock rom via Odin .
RootedNote3 said:
Hi. I am not an experienced rooter, but I managed tp root my Samsung Note3 a few years ago using Odin and some files I found here on the XDA site. I haven't used it for a couple of years.
I now need a second phone purely for work and wonder if the phone is safe enough to use today. I keep hearing things about newer phones and security updates, and am fearful of using the phone in case it is unsafe in some way.
Also, I have deleted some programs the playing with it, and don't know if I have messed it up.
Can I flash the phone again, and will a new file reinstall the whole operating system?
I don't mind buying a new phone if I have to, but love the idea of making the phone do what I want it to do rather than being told how it can be used by the manufacturer. The trouble is, I'm not an expert, and am unsure what I am doing. I love the Note3 and would love to feel safe enough to use it with an email account without the fear of my data being stolen by hackers.
Any thoughts would be gratefully received, thanks.
Click to expand...
Click to collapse
You're in luck.
The Galaxy Note 3 is fully supported on LineageOS. So, back up all your stuff, then use Heimdall or Odin to get TWRP (called the "recovery") installed on the machine. Then, download a copy of LineageOS as a ZIP file onto a little SD card and pop the card into the machine. Then, boot to TWRP and tell TWRP to install the nice new LineageOS. You can also install something called GApps which is all that Google infrastructure ****e too if you want. You'll find your phone up-to-date, secure and faster.
Hi archimime. I have managed to put two separate versions of lineageos onto an sd card and boot to the images. Both were one image at a time. On both occasions, I received a message saying:
E:failed to verify whole-file signature
E:signature verification failed
I have no idea what to do next. Any ideas would be appreciated.
I feel that I am so close to getting it to work again, but don't really know what I am doing here.