Related
UPDATE: See post #5 for the fix. It's really simple!
Hi,
First of all, I've been using this website as a resource for the last couple years. THANK YOU to all of you who dedicate your free time to helping the Android community!!!
K, now on to the issue:
This isn't my first rodeo. I'm not a dev, but I have a lot of experience with the Verizon S3. This is the second one I've owned, and I bought it off of craigslist. I'm starting to wonder if there's something wrong with the internal memory.
Stock recovery works perfectly, but both ClockworkMod and TWRP cannot mount anything -- cache, data, internal/external SD, etc.
My only computer is a MacBook Pro, and I have been using Odin 3.07 running inside a VMWare Fusion virtual machine running Windows 8.1. Luckily, Odin gets me back to stock every time, but I really need to get a custom recovery so I can get away from Touch Wiz.
I have tried 2 different versions of Casual as well as manually pushing everything through Odin.
jmsclbwmn said:
Hi,
First of all, I've been using this website as a resource for the last couple years. THANK YOU to all of you who dedicate your free time to helping the Android community!!!
K, now on to the issue:
This isn't my first rodeo. I'm not a dev, but I have a lot of experience with the Verizon S3. This is the second one I've owned, and I bought it off of craigslist. I'm starting to wonder if there's something wrong with the internal memory.
Stock recovery works perfectly, but both ClockworkMod and TWRP cannot mount anything -- cache, data, internal/external SD, etc.
My only computer is a MacBook Pro, and I have been using Odin 3.07 running inside a VMWare Fusion virtual machine running Windows 8.1. Luckily, Odin gets me back to stock every time, but I really need to get a custom recovery so I can get away from Touch Wiz.
I have tried 2 different versions of Casual as well as manually pushing everything through Odin.
Click to expand...
Click to collapse
It should work. Once latest version of casual is done try upgrading to latest version of whichever recovery you are gonna use. All the recoveries in casual are out of date and may just need to reflash recovery. Sounds like gonna use AOSP base so might as well stick with CWM as that is what you are going to end up with and what the AOSP devs support. While on TW can try upgrading it also as it the dev preferred recovery on TW. Shouldn't be the Mac if everything is actually unlocked, rooted and is flashing a recovery.
prdog1 said:
While on TW can try upgrading it also as it the dev preferred recovery on TW.
Click to expand...
Click to collapse
Can you please clarify this particular thought for me? I understood everything else.
jmsclbwmn said:
Hi,
First of all, I've been using this website as a resource for the last couple years. THANK YOU to all of you who dedicate your free time to helping the Android community!!!
K, now on to the issue:
This isn't my first rodeo. I'm not a dev, but I have a lot of experience with the Verizon S3. This is the second one I've owned, and I bought it off of craigslist. I'm starting to wonder if there's something wrong with the internal memory.
Stock recovery works perfectly, but both ClockworkMod and TWRP cannot mount anything -- cache, data, internal/external SD, etc.
My only computer is a MacBook Pro, and I have been using Odin 3.07 running inside a VMWare Fusion virtual machine running Windows 8.1. Luckily, Odin gets me back to stock every time, but I really need to get a custom recovery so I can get away from Touch Wiz.
I have tried 2 different versions of Casual as well as manually pushing everything through Odin.
Click to expand...
Click to collapse
You must have a newer GS3, the newer devices (made within the past few months) have a higher revision internal card reader that breaks some recoveries. (I know because I flashed a sprint gs3 that had the same exact issue).
The fix for this is to have a recovery built with the fix in it, which is upstream in the cm-10.2 kernel, but not in any official recoveries yet.
Let me see if I can find the exact commit for you... I know invisiblek fixed it
EDIT: heres the sprint thread of info (DO NOT FLASH THE FILES THO THEY WILL MESS UP THE VZW GS3)
http://forum.xda-developers.com/showthread.php?t=2391616&page=31
I found another thread on here with a guy having the exact same issue. That thread combined with the above information about outdated recovery images guided me to my solution. Here's how simple it was:
1) Use Casual to root/unlock.
2) Download Flashify
3) Download most recent ClockworkMod Recovery image
4) Use Flashify to flash said image
I really hope this info helps someone else!
jmsclbwmn said:
I found another thread on here with a guy having the exact same issue. That thread combined with the above information about outdated recovery images guided me to my solution. Here's how simple it was:
1) Use Casual to root/unlock.
2) Download Flashify
3) Download most recent ClockworkMod Recovery image
4) Use Flashify to flash said image
I really hope this info helps someone else!
Click to expand...
Click to collapse
Oh man! Thanks for posting how you got it to work. I've been trying to figure out what to do for almost 2 days.
I would of probably still be googling away if I hadn't found this. Thanks!
Sorry if this has been cover anywhere else, I can't find it.
I'm trying to use ADB TOOLKIT and it can't see my phone. I've installed the drivers multiple times & the install is successful. I can see the phone under my computer and when I change to RMNET + DM + MODEM, I can see the com port it is assigned to. I can move files around flash... etc.
Tool kit, qpst & other ADB utilities just don't see it. Some will even lock up requiring me to kill the attempt in task manager.
SCH-I535
4.1.2
I535VRBMF1
Cleanrom 6.0 R2
TWRP
win7 home premium
64 bit athlon
Any ideas?
Still working on it...
cntryby67 said:
Sorry if this has been cover anywhere else, I can't find it.
I'm trying to use ADB TOOLKIT and it can't see my phone. I've installed the drivers multiple times & the install is successful. I can see the phone under my computer and when I change to RMNET + DM + MODEM, I can see the com port it is assigned to. I can move files around flash... etc.
Tool kit, qpst & other ADB utilities just don't see it. Some will even lock up requiring me to kill the attempt in task manager.
SCH-I535
4.1.2
I535VRBMF1
Cleanrom 6.0 R2
TWRP
win7 home premium
64 bit athlon
Any ideas?
Click to expand...
Click to collapse
From everything I'm reading, I may need to take this thing back to 4.0.4 stock, make my repairs, then re-root & start over. Does this seem right, seems like a lot of trouble to get this thing working again.
I just can't understand why my PC sees it, but I can't use a com port.
Really could use some assistance from some of you extremely knowledgeable folks. I've managed to root this thing & my note 3 with help from instructions on here. I paid hard earned money for these devices I feel like I should be able to use it the way I want.
Dang, now even Odin freezes up when I try to connect to the phone.
Donations available upon success.
anyone?
I haven't had a chance to work on this yet, had some family issues that took me out of town.
Anyone have any ideas?
I'd like to not have to wipe everything. just to find out that wasn't the issue to begin with.
Anyone?
Tech Specs:
Processor Type: Quad-Core Cortex A9 Processor(When I turn on the tablet it says Allwinner A31?)
Processor Speed: 1.20 GHz
System Ram: 1 GB
Hard Drive Size: 8GB
Laptop Screen Size: 7 inch
Screen Type: Capacitive Touch Display
Battery Life: 4 hours
Battery Type: 2800mAh Lithium Ion
Network Connection: 802.11b/g/n Wireless LAN
Connector Type: 1 x HDMI, 1 x Headphone, 1 x MiniUSB 2.0
Operating System: Google Android
Accessories Included: AC Adapter,USB Cable
Operating System Version: Android 4.2 Jelly Bean
This thread is a continuation of some of the discussion that was from this thread: http://forum.xda-developers.com/showthread.php?t=2568427
While not at all high end tablets, it's always fun to see what can be squeezed out of them! As stated in the title, this thread will be regarding the following devices: Nobis NB07, Iview 774TPC, and DA-741QHD (which all appear to be the same hardware) rooting and ROMs. That should be pretty simple for now since, we currently have no ROMs and no proven root method. Some have reported success using the Kingoapp. If anyone is able to obtain root, we would like to ask that you make a copy of the firmware and upload it for those of us having trouble doing so. After doing so, we can modify it and hopefully get more our of the software.
You may also post information regarding tweaking the ROMs for these devices and other ways to make them more useful!
Warning: The following may have unforseen effects including breaking your tablet to the point of being unrepairable.
Option #1, Use KingoApp Some users have reported that this did not work for them, at least one user reported that it did.
Instructions per RawX:
For the drivers the easiest method is just using Top Notch Tablets How to install ADB drivers. That worked on the first one, the second one it didn't not entirely sure why, but you can send a email to support and ask them for development drivers for the nobis tablets and they will send the ADB drivers you need. After you have the drivers installed use kingo while the tablet is in usb debug mode BEFORE plugging it into your usb port and do not turn on usb transfer. the first time after it reboots kingo will report that it was not rooted, leave it plugged in and power off and back on and it should report the root worked. This method gives you SuperSU. Both times. I've done this were for clients of mine but its pretty straight forward.
Click to expand...
Click to collapse
The working drivers for me were: VID_1f3a_PID_efe8
Please consider trying this first and give us some feedback. A word of warning though, there has been some discussion on XDA in the past that this may be malware though I'm not sure this was ever confirmed.
Option #2, Flash firmware for an alternate device that can be rooted easily. Warning!!! Currently, there is no way to get back to stock (until someone who gets root with another method makes a copy of the firmware)
Go to this website: http://www.iviewus.com/firmware788TPC/ and download the firmware. Yes, it is for another tablet. However, the tablet appears to have the same specs as ours. Once downloaded. Install the included PhoenixSuit software. Once it is running, click the button at the bottom right to update the software to the newest version (this may not be required). Then, plug in your tablet using the usb port and install the drivers. I used google and found them all within minutes. Once the software recognizes your tablet go to the firmware tab where you have extracted the .img file and select the file. Next, click upgrade to upgrade your tablet (it has instructions to help your tablet be recognized if you are having difficulty). Once the new firmware has been flashed, then download the file RootFromOTA.zip that can be found on various places such as XDA. Move the file onto an external SD card. Then, go to settings -> backup & reset -> Recovery Mode. Your tablet will restart. Once it does, select the bottom option to install from SD card. Install the RootFromOTA.zip and then reboot. Once rebooted, install the supersu app or another root application of your choice.
Credits: As above to RawX
Congrats... You're rooted.
Mods
Currently, I've managed to get great battery life out of my tablet by installing kernel tuner and changing the settings as such:
Governor: Ondemand (default is fantasys)
Max: 1200 MHz (Default is 1200 MHz)
Min: 240 MHz (Default is 120 MHz, but I had trouble with usability at this setting and Ondemand)
I also recommend setting wifi to turn off when the screen is off and turn off autosync.
This seemed to give me a very useable system but with greatly improved battery life. Doing the above and a few other tweaks here and there have made my battery life so that it drains by about 1% overnight when not in use. I also seem to get better battery life while using the tablet. I haven't had any trouble playing games either.
neatojones said:
Option #2, Flash firmware for an alternate device that can be rooted easily. Warning!!! Currently, there is no way to get back to stock (until someone who gets root with another method makes a copy of the firmware)
Go to this website: http://www.iviewus.com/firmware788TPC/ and download the firmware. Yes, it is for another tablet. However, the tablet appears to have the same specs as ours. Once downloaded. Install the included PhoenixSuit software. Once it is running, click the button at the bottom right to update the software to the newest version (this may not be required). Then, plug in your tablet using the usb port and install the drivers. I used google and found them all within minutes. Once the software recognizes your tablet go to the firmware tab where you have extracted the .img file and select the file. Next, click upgrade to upgrade your tablet (it has instructions to help your tablet be recognized if you are having difficulty). Once the new firmware has been flashed, then download the file RootFromOTA.zip that can be found on various places such as XDA. Move the file onto an external SD card. Then, go to settings -> backup & reset -> Recovery Mode. Your tablet will restart. Once it does, select the bottom option to install from SD card. Install the RootFromOTA.zip and then reboot. Once rebooted, install the supersu app or another root application of your choice.
Congrats... You're rooted.
Click to expand...
Click to collapse
I am assuming the camera is not working using this method or did you figure it out?
And also, do you have a link to the drivers you used off hand or what did you search for to find them?
Hippie459MN said:
I am assuming the camera is not working using this method or did you figure it out?
And also, do you have a link to the drivers you used off hand or what did you search for to find them?
Click to expand...
Click to collapse
Nope, still haven't gotten the camera working. We are missing some config files still. Do you need the camera drivers or the tablet drivers?
The camera drivers are : sp2518 and sp0838, though I also see a module being loaded called cam_detect
I don't recall where I got the adb usb drivers for the tablet, but it would probably be a good thing to mention in this thread so if you have them, let me know and I can add it to one of the top posts. If you're having trouble finding them, I'll remove my drivers and go back through the process to find them again.
Looking for the tablet drivers. I am about ready to tap out on this thing for a while. lol Its driving me crazy.
Hippie459MN said:
Looking for the tablet drivers. I am about ready to tap out on this thing for a while. lol Its driving me crazy.
Click to expand...
Click to collapse
OK. The drivers I used were probably: VID_1f3a_PID_efe8 (or something similar)
You can either google that or try downloading the firmware for TP718AQ here: http://www.agptek.com/forum/viewtopic.php?f=22&t=948
Remove all prior drivers for the tablet. Plug it in and tell Windows to use the drivers from the extracted file you download (Will extract to TP718AQ_Update_Firmware\USB Driver).
Sometimes I have to do a little dance with restarting the device and my computer to get it to recognize it.
As a last resort you could try this: http://www.xda-developers.com/andro...r-solves-your-adb-driver-problems-on-windows/
Let me know if you have any problems.
Good Luck!
Ok, I officially give up trying to root this thing. Stupid windows will not install the drivers in both the links you provided and I cant get windows to even try to install anything after removing them then I got the android ADB drivers to install but still zero luck. All rooting apps fail. Hopefully someone will post the image of their rooted NB07. A few claim to have rooted it just fine but I cant win with this thing.
All I want is to be able to run link2sd and a few other apps that require root. This is officially the longest I have owned an un-rooted android device. lol
I'm the one that got the root working using kingo, so for the drivers the easiest method is just using Top Notch Tablets How to install ADB drivers ( I would post a link but I don't have 10 posts yet on XDA)
That worked on the first one, the second one it didn't not entirely sure why, but you can send a email to support and ask them for development drivers for the nobis tablets and they will send the ADB drivers you need. After you have the drivers installed use kingo while the tablet is in usb debug mode BEFORE plugging it into your usb port and do not turn on usb transfer. the first time after it reboots kingo will report that it was not rooted, leave it plugged in and power off and back on and it should report the root worked. This method gives you SuperSU. Both times I've done this were for clients of mine but its pretty straight forward.
Well, I have decided that for now this tablet of mine is un-rootable. I must have tried with 5 or 6 different drivers about 20 times with each with Kingo. I even tried that other program that is all in Chinese that loads some BS app on to your phone with no luck. So, for now, I am going to give up but if anyone has any other ideas or wants me to try something or they have for sure figured out how to root it, let me know as I am happy to help the best I can.
Edit: Oh yeah, Dont know how much this will help anyone but here is some more specific specs on the Nobis NB07 tablet I pulled off it with Hardware Info 3.0.0. Feel free to put the link in the first or second post if you want. Maybe it will help a little bit more.
http://www.hippie459mn.com/nobis_nb07/index.html
:good:
Hippie459MN said:
Well, I have decided that for now this tablet of mine is un-rootable. I must have tried with 5 or 6 different drivers about 20 times with each with Kingo. I even tried that other program that is all in Chinese that loads some BS app on to your phone with no luck. So, for now, I am going to give up but if anyone has any other ideas or wants me to try something or they have for sure figured out how to root it, let me know as I am happy to help the best I can.
Edit: Oh yeah, Dont know how much this will help anyone but here is some more specific specs on the Nobis NB07 tablet I pulled off it with Hardware Info 3.0.0. Feel free to put the link in the first or second post if you want. Maybe it will help a little bit more.
http://www.hippie459mn.com/nobis_nb07/index.html
:good:
Click to expand...
Click to collapse
Thanks to the work of someone on another forum, I have now got TWRP working on our device and am hoping we will soon have a CM working on it as well. Check back in the near future for further details. Maybe if you can't have a rooted stock, we can get a fully functional CM.
I am assuming you need to have root to flash the TWRP recovery correct. This is good news. Would love to have more info on it. Are you working with people on this site or another site? I would love to follow along.
Hippie459MN said:
I am assuming you need to have root to flash the TWRP recovery correct. This is good news. Would love to have more info on it. Are you working with people on this site or another site? I would love to follow along.
Click to expand...
Click to collapse
On another site for now. Just PM's at the moment so not much to follow yet. But, all you'll need is the Phoenixsuit to install it, so you won't have to root your tab first. You'll have root on the new ROM. You'll have to have drivers fully working though. Once fully working I'll link to the site so people can get the files and hopefully we can get this guy some donations for his work.
Awesome! I would go right to CM on this and skip the whole rooting the stock firmware. Would be nice to be able to root the stock firmware though then things would be so much easier. Think the camera will be working on the CM build? If not no big deal but would be nice to have them working.
Keep me (us) posted on the progress.
Hippie459MN said:
Awesome! I would go right to CM on this and skip the whole rooting the stock firmware. Would be nice to be able to root the stock firmware though then things would be so much easier. Think the camera will be working on the CM build? If not no big deal but would be nice to have them working.
Keep me (us) posted on the progress.
Click to expand...
Click to collapse
Not sure about the camera yet. I have CM booting but no touch yet, so this will be the first task. I'll keep everyone posted.
Any word on getting things to work yet?
Currently, we have CM working with no touch screen/camera. I'm not sure what else all isn't working because I'm waiting on my OTG cable to come in for further testing to see what all is going to be required to get the touchscreen going. Right now, it appears we my be looking at compiling our own drivers which could take some time to do. I think we'll get it eventually, but it may take some time. If you don't need touchscreen or camera, it could be working right now.
Sorry for no updates for a while. My work has been delayed on this since I have a son who is sick and in the pediatric ICU. I'll get back to work when things calm down for me.
No worries man. Family first.
Just a question, Hippie...
On the original ROM, can you see your device in ADB? If you can, and type "adb shell" do you get root? If you have adb access but not root, can you try typing sh and see what happens?
Also, could you try loading the rootfromOTA.zip and see if you can get a printout of the error log if possible?
Also, I tried installing this from the recovery on a similar ROM and it acted like it failed. I went back into the ROM and used adb and was able to get root using vroot or kingo...I don't remember which. This may be worth a shot.
Interestingly, I have been looking for alternative ways to root and found this (but we need to find a way to get to the bootloader):http://whiteboard.ping.se/Android/Rooting
I think that the method to get to bootloader is to turn off the tablet, then hold down the back button while tapping the power button 5 times. But, I also googled and found a method for getting to fastboot from adb in android without root as well which may work.
I sold my tf700 to a friend, and let him know: Do not factory reset through the Android settings. Well, He passed it on to someone else, and forgot to mention this. So, that whole TWRP bootloop scenario exists. Dug through forums, found a post where someone had made some file that resets the boot process to not go immediately to TWRP or something, IIRC, but regardless, I've got a custom-made solution, and even wrote a batch file to automate the thing (given the amount of time you have the TWRP screen before it reboots) much like the OP had.
Here's the problem: my desktop doesn't recognize the usb device when I plug in to windows. IIRC, I'd always had some kinda issue with that version of TWRP, but I never addressed that, and that fell by the wayside apparently. I don't have time to sanitize my PC and re-establish the ASUS driver environment or other advanced trickery or whatever, and I just sold my laptop prior to trying on that. My question to you fine folks is this: If I were to install Ubuntu or some other Linux-based environment, would my odds increase in terms of being able to coax TWRP to be recognized so I can flash this tiny little file over and get the thing back running? Apparently windows just doesn't want to, and short of being able to put a newer TWRP on the device, I've got to establish a usb connection somehow.
TIA :good:
monogwai said:
I sold my tf700 to a friend, and let him know: Do not factory reset through the Android settings. Well, He passed it on to someone else, and forgot to mention this. So, that whole TWRP bootloop scenario exists. Dug through forums, found a post where someone had made some file that resets the boot process to not go immediately to TWRP or something, IIRC, but regardless, I've got a custom-made solution, and even wrote a batch file to automate the thing (given the amount of time you have the TWRP screen before it reboots) much like the OP had.
Here's the problem: my desktop doesn't recognize the usb device when I plug in to windows. IIRC, I'd always had some kinda issue with that version of TWRP, but I never addressed that, and that fell by the wayside apparently. I don't have time to sanitize my PC and re-establish the ASUS driver environment or other advanced trickery or whatever, and I just sold my laptop prior to trying on that. My question to you fine folks is this: If I were to install Ubuntu or some other Linux-based environment, would my odds increase in terms of being able to coax TWRP to be recognized so I can flash this tiny little file over and get the thing back running? Apparently windows just doesn't want to, and short of being able to put a newer TWRP on the device, I've got to establish a usb connection somehow.
TIA :good:
Click to expand...
Click to collapse
Well yes and no.
Linux works much better with adb/fastboot, but if it it easier to install Linux and get it working if you have never used it compared to getting Windows drivers working - idk....
berndblb said:
Well yes and no.
Linux works much better with adb/fastboot, but if it it easier to install Linux and get it working if you have never used it compared to getting Windows drivers working - idk....
Click to expand...
Click to collapse
I figured that would probably be the case. Now, it's been several years since I've used Linux (Ubuntu Feisty Fawn was the last time I used Linux, and that was just to hack a first gen Xbox), but i'm a command-line based OS guy from the days of old, so I oughta be okay. I'm sure one of the various and sundry tutorials here on xda will help should I get stuck.
So, that being said, I guess I just need to install a distro and grab some adb/fastboot drivers for Linux? Or is that all built in? Is the command line interface sufficient, or will I need some GUI like xwindows (sorry if my info is horribly dated, lol.)
I'd probably better do some reading.
Nobody has any more expertise to proffer?
monogwai said:
Nobody has any more expertise to proffer?
Click to expand...
Click to collapse
I cam across this live distro recently and the dev included the tools needed for adb fastboot. It works great! https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
There also several Puppy Linux distros out there which may be interesting since they offer persistent mode already but afaik you have to download the adb fastboot binaries yourself. But that's it - no drivers needed.
With those installed you just need as terminal window. No other gui necessary
berndblb said:
I cam across this live distro recently and the dev included the tools needed for adb fastboot. It works great! https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
There also several Puppy Linux distros out there which may be interesting since they offer persistent mode already but afaik you have to download the adb fastboot binaries yourself. But that's it - no drivers needed.
With those installed you just need as terminal window. No other gui necessary
Click to expand...
Click to collapse
This is just the tip I needed. Big thanks!
Well, i assembled the troops- universal naked driver and minimal adb/fastboot on a fresh win 8.1 install. Bootit.ko file in my adb folder. Opened adb, plugged in tablet. Twrp starts. Hear the USB plug in noise, so adb is ready. Adb devices command, shows up recovery like it should. I then run a batch command to automate:
adb push bootit.ko /sdcard/
adb shell insmod /sdcard/bootit.ko
... as per the directions. I get this in response:
adb: error: connect failed: protocol fault <couldn't read status>: no error
on the first command, and 'no device found' on the second.
Now what?
Edit: nevermind. Added 'adb devices' to the batch file and it did it fast as anything. Lol.
New kink: adb command succeeded and i got fastboot access. Formatted 'misc' partition and rebooted-- still with the bootloop. I can still access fastboot, but that's it. Twrp always restarts. So, did SWIM bork the recovery partition too? Wondering if I should try re-flashing twrp, or downloading the original ASUS blob file and restarting from square one?
Edit:
Got impatient, started trying things. Links found thru the forums pointing to original ASUS rom blob are all broken, so i settled for starting with twrp. Downloaded freshest version from twrp.me compatible with the device and flashed it-- same result upon attempting to open twrp.
Took a break. Thought about it, and decided to fastboot erase recovery, and try flashing twrp again. Probably not a great idea... Now I get
Sending 'staging' <7210 kb>...
FAILED <data transfer failure (unknown error)>
So I guess there's a step after erasing to re-init the partition or something?
Just a note to anyone lurking - don't do stuff if you're only half-informed. You can be stupid and impatient like me and have broken stuff.
Impatience is a very bad advisor...
As long as you have fastboot you should be ok. Asus seems to have messed with their website again or they finally took the support pages down permanently.
I have a copy on my server and can upload it tonight.
Patience my friend, patience
berndblb said:
Impatience is a very bad advisor...
I have a copy on my server and can upload it tonight.
Patience my friend, patience
Click to expand...
Click to collapse
This is too true. That's why I threw in that little blurb. :good:
I'll await your link with bated breath.
Ok here's the 10.6.1.14.10 firmware:
https://www.androidfilehost.com/?fid=817550096634791660
Don't forget to check the md5 once downloaded
You may de-bate your breath again
berndblb said:
Ok here's the 10.6.1.14.10 firmware:
https://www.androidfilehost.com/?fid=817550096634791660
Don't forget to check the md5 once downloaded
You may de-bate your breath again
Click to expand...
Click to collapse
Debate my breath? Well, my breath reeks of Marijuana... I think it's a liberal.
Lol
Just a question: since I'll be repopulating all the partitions with the stock blob, does that affect my unlocked bootloader, or is it gonna be straight up manufacturer reset? I'm sure that's covered in the threads that address the 'buster99' process, but I need to go locate the thread. I didn't fully digest the thread as i'd yet to find the blob I could d/l, until you hooked it up. ?
No, you cannot relocate the bootloader. Flash away
berndblb said:
No, you cannot relocate the bootloader. Flash away
Click to expand...
Click to collapse
Ugh, corrupt archive. ? trying to download from a different server this time.
Edit: same results w/new download. Repairing the archive didn't help either.
Asus, ya'll are killing me! Every link on the interweb linking to a TF700 firmware is broken, and all that can be found are for the 700kl.
Final update:
Found a valid download link for 10.6.1.14.8. Had some difficulties with it (revived the post on the buster99 process) -- followed as written, and had a fail on the last process <invalid state>. Being super impatient (mentioned *that* before, lol), I decided to try and reestablish twrp, as that was the original issue. That took! Flashed 3.0.0-1 (iirc), was able to open twrp, but couldn't mount system or anything. So I formatted the crap out of all partitions, converted /data to f2fs, and was able to successfully flash katkiss nougatella. Wiped the caches, rebooted, and I'm golden! 3 months later, and it finally works.
Moral of the story: don't sell rooted devices to ppl who don't understand what that entails. You can tell a person till ur blue in the face, NO FACTORY WIPE VIA ANDROID -- Odds are, they'll forget. Worked out for me in the long run (took back the 700 and gave a 201 as replacement), but i was never sure I'd come out clean on the other end.
I have similar problem, i can't even go to bootloader.
Just keep bootlooping. Is there any chance of reviving my tf700t?
If yes please advice me step by step process to do that.
Thanks
Not enough information. What can you get to?
What's your ROM, bootloader, recovery?
berndblb said:
Not enough information. What can you get to?
What's your ROM, bootloader, recovery?
Click to expand...
Click to collapse
Thanks you already help on other thread.
It's a long story how this happened.
By the way I was running nougtell version don't remember as it happened in January.
I wanted to transfer some video files on my usb 2tb hard drive, so I did usb otg connection to my tab, i did this thing before and I use es file explorer to do the transfer, few occasions es file hang or whole tablet hang so I have to restart. But in January when this thing happened it just went into bootlooping i can go to fastboot but not recovery or android.
Then I search on many thread i couldn't find any working solution.
My cable was not detecting tab so I couldn't able to push recovery., But the same cable was ok for charging.
Then I bought new cable from eBay it took around a month to arrive.
But in mean time being impatient i tried data wipe from bootloader.
Then even i couldn't able to bootloader after that.
I know being impatient with doing something like this is not good you have to suffer.
Bootloader was latest version .14 at the end and recovery was 3.0.1
Using nogtella rom
Thanks
I need some help.
I am running a Linux system and am trying to flash the firmware on my Samsung phone.
Odin is out because, while I can start it via emulator, it will never be able to actually communicate with the phone via usb.
JOdin3, which is java and platform-independent, sees my phone, communicates with it... and insists that every blessed file I feed it is corrupt. Straight from Samsung's own website? 'Corrupt,' according to JOdin3.
Heimdall. Ah, yes, Heimdall of the elusive 'Heimdall Firmware Packages' that nobody seems able to explain how to make.
I have spent days of my life systematically hunting all this down across dozens of websites, figuring out how to get Odin, JOdin3, Heimdall, Samfirm, Samloader and I can't think what others working on my OS, only to find that every one of these programs breaks in the end.
Is this firmware flashing thing just a big joke? Or is it actually possible?
micheal3chaife said:
I need some help.
I am running a Linux system and am trying to flash the firmware on my Samsung phone.
Odin is out because, while I can start it via emulator, it will never be able to actually communicate with the phone via usb.
JOdin3, which is java and platform-independent, sees my phone, communicates with it... and insists that every blessed file I feed it is corrupt. Straight from Samsung's own website? 'Corrupt,' according to JOdin3.
Heimdall. Ah, yes, Heimdall of the elusive 'Heimdall Firmware Packages' that nobody seems able to explain how to make.
I have spent days of my life systematically hunting all this down across dozens of websites, figuring out how to get Odin, JOdin3, Heimdall, Samfirm, Samloader and I can't think what others working on my OS, only to find that every one of these programs breaks in the end.
Is this firmware flashing thing just a big joke? Or is it actually possible?
Click to expand...
Click to collapse
I'm a part-time Linux user also but I can't say that I've ever had luck with using Heimdall to flash Samsung devices. Many people have used it and had success but for me it has always been a pain getting the right "extra" packages installed and configured correctly for Heimdall to function correctly, it involves more than just installing and running Heimdall.
In my experience, Odin on a Windows PC is hands down the best way to go for flashing Samsung Devices.
Also, when you say they all fail in the end, what do you mean? Are they not working at all or are you able to begin the flash but it fails before it finishes the flash?
Droidriven said:
I'm a part-time Linux user also but I can't say that I've ever had luck with using Heimdall to flash Samsung devices. Many people have used it and had success but for me it has always been a pain getting the right "extra" packages installed and configured correctly for Heimdall to function correctly, it involves more than just installing and running Heimdall.
In my experience, Odin on a Windows PC is hands down the best way to go for flashing Samsung Devices.
Also, when you say they all fail in the end, what do you mean? Are they not working at all or are you able to begin the flash but it fails before it finishes the flash?
Click to expand...
Click to collapse
Hi, thanks for the sympathetic response (read: 'shouder to cry on').
"Break" in the sense that eventually, each of the programs I have tried - Heimdall, JOdin3, and Odin - have shown errors that, so far, have proven fatal:
*Heimdall requires 'Heimdall Packages' that seem to exist nowhere
*Odin fails to communicate with the phone
*JOdin3 returns a 'corrupted file' message when one directs it to the firmware to upload and flash. This issue has been reported to the maintainer's github as of 12 days ago, meaning it is a very recent issue.
The Heimdall issue *may* have a workaround - one can try, as per the maintainer's instructions on his github, feeding the component files one by one to the main process. I will try that.
A further possibility lies in the fact that previously, I had not enabled 'USB debugging' on the phone itself, which may or may not help with the interface.
There is also ADB, which I took a cursory look at last night. ADB appears to be able to work to move packets between a computer and a phone.
There is the option, on Samsung phones, to 'Appy update from SD card', which is what I propose to try now.
Latly, there is the option of installing an entirey different OS on the phone, and to hell with Android (?).
I will keep all you folks who are now rooted to the edge of your seats updated as things move along.
micheal3chaife said:
Hi, thanks for the sympathetic response (read: 'shouder to cry on').
"Break" in the sense that eventually, each of the programs I have tried - Heimdall, JOdin3, and Odin - have shown errors that, so far, have proven fatal:
*Heimdall requires 'Heimdall Packages' that seem to exist nowhere
*Odin fails to communicate with the phone
*JOdin3 returns a 'corrupted file' message when one directs it to the firmware to upload and flash. This issue has been reported to the maintainer's github as of 12 days ago, meaning it is a very recent issue.
The Heimdall issue *may* have a workaround - one can try, as per the maintainer's instructions on his github, feeding the component files one by one to the main process. I will try that.
A further possibility lies in the fact that previously, I had not enabled 'USB debugging' on the phone itself, which may or may not help with the interface.
There is also ADB, which I took a cursory look at last night. ADB appears to be able to work to move packets between a computer and a phone.
There is the option, on Samsung phones, to 'Appy update from SD card', which is what I propose to try now.
Latly, there is the option of installing an entirey different OS on the phone, and to hell with Android (?).
I will keep all you folks who are now rooted to the edge of your seats updated as things move along.
Click to expand...
Click to collapse
USB debugging makes a difference. Have you tried using older or different versions of Heimdall?
Are you running a VM to run windows and windows programs on linux or are you using wine to run windows programs? Wine doesn't work well enough to make it a viable option to run Odin.
I really suggest you bite the bullet and use a Windows system to use Odin. As long as you haven't corrupted any of the partitions on the device, flashing via Odin on a Windows PC will be effortless, a few clicks and a few minutes, done and done.
I think it could be dependent on the quality of the packages built by the packagers for your distro as to whether 'heimdall' works for you. I recently flashed LineageOS (2 days ago) on my old Galaxy Note 10.1 (2014) tablet using heimdall. I posted about it here: https://forum.xda-developers.com/f/galaxy-note-10-1-2014-edition-q-a-help-troubl.2502/
Note that hardware aspects such as a quality USB cable can at times be issues, and you may have better luck using a PC's USB-2 port instead of a USB-3 port.
In my case, for openSUSE LEAP-15.2 I successfully used heimdall-1.4.2
I also used android-tools-9.0.0 packaged for same openSUSE version, which provided 'adb' and 'fastboot'. While 'adb' worked for me, I could not not get 'fastboot' to detect my tablet when the tablet was in 'Odin' mode - and hence I could not flash with 'fastboot'. Fortunately heimdall did detect the Tablet when the Tablet was in 'odin' mode, and I was thus able to flash TWRP from 'heimdall'. I note specifying 'RECOVERY" in 'heimdall' did not work for me, but instead specifying the 'Entry' location for the flash (after checking the PIT) did work for me. Again, documented the details in that thread above.
In all cases on my GNU/Linux I used command line and not GUI front ends.
Goodl luck in your efforts.
Droidriven said:
USB debugging makes a difference. Have you tried using older or different versions of Heimdall?
Are you running a VM to run windows and windows programs on linux or are you using wine to run windows programs? Wine doesn't work well enough to make it a viable option to run Odin.
I really suggest you bite the bullet and use a Windows system to use Odin. As long as you haven't corrupted any of the partitions on the device, flashing via Odin on a Windows PC will be effortless, a few clicks and a few minutes, done and done.
Click to expand...
Click to collapse
I do not have ready access to a Windows machine, alas... Thanks for the other suggestions. Yes, I've been trying with wine, but with USB debugging disabled. My next attempt will probably be with Heimdall + USB debugging.
If I go the VM route, do you have a suggestion on how to set that up?
RE: Heimdall, I was under the impression that the most recent version (1.4.2, if I'm not mistaken) is best.
Again, thanks for the imput. Wish me ... maybe not luck, but continued systematic determination. And a little common sense.
You can run ADB wirelessly, means over Wi-Fi. So no Windows machine is required.
xXx yYy said:
You can run ADB wirelessly, means over Wi-Fi. So no Windows machine is required.
Click to expand...
Click to collapse
I"m not sure that helps them.
micheal3chaife said:
Heimdall. Ah, yes, Heimdall of the elusive 'Heimdall Firmware Packages' that nobody seems able to explain how to make.
....
Is this firmware flashing thing just a big joke? Or is it actually possible?
Click to expand...
Click to collapse
I hope you managed to finally succeed.
'Fresh' on the successful install of LineagOS-14.1 on my Samsung Galaxy-10.1 (2014) using adb and Heimdall on openSUSE-LEAP-15.2 (v.1.4.2 of heimdall) I then a couple of days ago proceeded to install LineageOS-14.1 on my wife's old Samsung Note-8 tablet.
As before, I pre-positioned the zip files for lineageOS and for GAPPS on her tablet, and then used heimdall to flash TWRP from my GNU/Linux PC.
it took me 3 attempts to flash TWRP, with the first failed attempted breaking the regular Android 4.1 boot to the Tablet, but fortunately it would still boot to the Tablet's recovery 'download' (flashboot) mode. The issue with the failures with me was a somewhat flaky USB cable. This is the best of about a dozen USB cables I own, and it works great for charging .... but for data transfer in a flash, my experience is the cable has to be very very VERY good. Note I was using a USB2 port.
Once TWRP was flashed, I tried to boot the Tablet to recovery mode, but the darn thing booted instead to the old Android 4.1. I was afraid that would wipe the TWRP, ... so I then with the Tablet still powered, ran 'adb' with appropriate recovery reboot options (from my GNU/Linux with Tablet connected), and the Tablet fortunately booted to TWRP (and it had not yet been wiped).
With TWRP running it was a simple matter to flash LineageOS and GAPPS. This time, BEFORE rebooting after the LineageOS/GAPPS flash, I was then careful to ensure TWRP re-flashed/installed, and it kept TWRP on the Samsung Galaxy Note-8. With my previous Samsung Galaxy Note-10.1 (2014) install I did not do that, and I had TWRP wiped after my reboot to LineageOS.
Again good luck in your efforts. I can say heimdall in GNU/Linux does work (together with adb).
micheal3chaife said:
I need some help.
I am running a Linux system and am trying to flash the firmware on my Samsung phone.
Odin is out because, while I can start it via emulator, it will never be able to actually communicate with the phone via usb.
JOdin3, which is java and platform-independent, sees my phone, communicates with it... and insists that every blessed file I feed it is corrupt. Straight from Samsung's own website? 'Corrupt,' according to JOdin3.
Heimdall. Ah, yes, Heimdall of the elusive 'Heimdall Firmware Packages' that nobody seems able to explain how to make.
I have spent days of my life systematically hunting all this down across dozens of websites, figuring out how to get Odin, JOdin3, Heimdall, Samfirm, Samloader and I can't think what others working on my OS, only to find that every one of these programs breaks in the end.
Is this firmware flashing thing just a big joke? Or is it actually possible?
Click to expand...
Click to collapse
Look here.