Any of the A100 talent, have the A110?
It's a decent machine for the price. It goes for around 150, comes with 8gb internal, expandable to 32g via micro SDHC, 1gig of RAM, Tegra 3 quad core @ 1.2ghz.
Only current issue, no recovery (I believe the recovery and kernel are combined), root method or ROMs available for this beast. There was a root tool for 4.1.1, but some have updated (for better ui enhancements) to 4.1.2, and there's no root option for it.
Just wondering if any of the A100 talent have this, it would be great to see this thing unleashed!
Sorry if anyone is upset about this being the wrong category/thread... Unfortunately, XDA has no dedicated thread for the A110, at this time.
heX79 said:
Any of the A100 talent, have the A110?
It's a decent machine for the price. It goes for around 150, comes with 8gb internal, expandable to 32g via micro SDHC, 1gig of RAM, Tegra 3 quad core @ 1.2ghz.
Only current issue, no recovery (I believe the recovery and kernel are combined), root method or ROMs available for this beast. There was a root tool for 4.1.1, but some have updated (for better ui enhancements) to 4.1.2, and there's no root option for it.
Just wondering if any of the A100 talent have this, it would be great to see this thing unleashed!
Sorry if anyone is upset about this being the wrong category/thread... Unfortunately, XDA has no dedicated thread for the A110, at this time.
Click to expand...
Click to collapse
No I went with a nexus 7, no unlocking is a deal breaker right off the bat with me. Plus I heard they didn't upgrade the screen or battery in it, two things I hated about the a100, and were also deal breakers for me.
Sent from my Galaxy Nexus using Tapatalk 2
Unlocking the BL is easy on the A110. I did it with adb.
heX79 said:
Unlocking the BL is easy on the A110. I did it with adb.
Click to expand...
Click to collapse
Then why no root? If its unlocked just flash a rooted stock ROM or something.
Sent from my Nexus 7 using Tapatalk 2
Nothing seems to be available, at the moment. I wouldn't know where to begin, compiling from source.
heX79 said:
Nothing seems to be available, at the moment. I wouldn't know where to begin, compiling from source.
Click to expand...
Click to collapse
Will it use an update.zip that's been changed if its unlocked?
Sent from my Thrive - Kuroikaze B19
Wouldn't know, there is an os upgrade file on acers page, the same image name as my current version (after updating to 4.1.2), can that be renamed to update.zip, modded and flashed? I've not used a stock recovery before lol.
Sent from the Tab
heX79 said:
Wouldn't know, there is an os upgrade file on acers page, the same image name as my current version (after updating to 4.1.2), can that be renamed to update.zip, modded and flashed? I've not used a stock recovery before lol.
Sent from the Tab
Click to expand...
Click to collapse
If its a zip file maybe if not its anyone's guess how to mess with it.
Sent from my Galaxy Nexus using Tapatalk 2
Yes it's a zip, 54MB in size, just an update from 4.1.1 to 4.1.2.
Name: OS_Acer_AV051.A110.RV00RC09.WW.CUS1_A41J_A.zip
File/Folder layout:
/firmware
/META-INF
/patch
/recovery
/system
blob
Download link, for anyone interested.
heX79 said:
Yes it's a zip, 54MB in size, just an update from 4.1.1 to 4.1.2.
Name: OS_Acer_AV051.A110.RV00RC09.WW.CUS1_A41J_A.zip
File/Folder layout:
/firmware
/META-INF
/patch
/recovery
/system
blob
Download link, for anyone interested.
Click to expand...
Click to collapse
Then do a quick signature test, add a random file into it then see if it flashes or not. Doesn't matter how big or what it is.
Sent from my Galaxy Nexus using Tapatalk 2
Need to add a new source for the A110 to get developers. Its still a new tab but the down side is the battery sucks and they never change the screen angle. I guess to keep it in the $200 mark. Then again the nexus 7 has no micro sd port, hdmi port, but the screen is so clear and it support otg.
Sent from my A100 using xda premium
pio_masaki said:
Then do a quick signature test, add a random file into it then see if it flashes or not. Doesn't matter how big or what it is.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I tried to add the Superuser.apk to the /system/app and SU to the /system/bin, but it gives a corruption error. I'll have to completely unzip it, add the files and re-zip in order to add them.
But to work in the stock recovery, I assume it would need to be renamed to update.zip, and placed on the internal /sdcard?
heX79 said:
I tried to add the Superuser.apk to the /system/app and SU to the /system/bin, but it gives a corruption error. I'll have to completely unzip it, add the files and re-zip in order to add them.
But to work in the stock recovery, I assume it would need to be renamed to update.zip, and placed on the internal /sdcard?
Click to expand...
Click to collapse
Probably external SD.
Sent from my Galaxy Nexus using Tapatalk 2
heX79 said:
I tried to add the Superuser.apk to the /system/app and SU to the /system/bin, but it gives a corruption error. I'll have to completely unzip it, add the files and re-zip in order to add them.
But to work in the stock recovery, I assume it would need to be renamed to update.zip, and placed on the internal /sdcard?
Click to expand...
Click to collapse
Did you make it? I am waiting to root my A110 as well.
OK well let's see. Is there a twrp or something for a510? I can see about making a twrp but its extremely risky without some precise information since I don't have one to even look at for information. I'll be somewhat willing to work a little to get it opened up but you'll all need to do the homework and be willing to test it. Recoveries are very dangerous potential brickers.
Or someone that owns one can do it.
Or someone can send me one. I'm not willing to sell my n7 for what I consider a downgrade (battery and screen), especially when I just started working on deving on it lol
Sent from my Nexus 7 - JBSourcery 4.1
sky007 said:
Did you make it? I am waiting to root my A110 as well.
Click to expand...
Click to collapse
I did make it, haven't used a auto-signer on the zip yet. Got a bit busy with family being over, for new years. So no I haven't attempted a flash yet; not that I believe this will actually root the device, as the updater-script/binary won't have been updated.
pio_masaki said:
OK well let's see. Is there a twrp or something for a510? I can see about making a twrp but its extremely risky without some precise information since I don't have one to even look at for information. I'll be somewhat willing to work a little to get it opened up but you'll all need to do the homework and be willing to test it. Recoveries are very dangerous potential brickers.
Or someone that owns one can do it.
Or someone can send me one. I'm not willing to sell my n7 for what I consider a downgrade (battery and screen), especially when I just started working on deving on it lol
Sent from my Nexus 7 - JBSourcery 4.1
Click to expand...
Click to collapse
I'm willing to test/give any and all info you may need. I figured a decent starting point might be from the download on Acers page, but I could be wong. I'm completely ignorant on porting a recovery. There is a dev that wrote a tool kit for the a110, but it only rooted 4.1.1. On 4.1.2 all it's capable of (at this time) is unlocking the BL. Some method of rooting was patched (from what I've gathered so far) in 4.1.2, so the tool kit was using some form of (now patched) exploit.
Update: Some better support in this thread: http://forum.xda-developers.com/showthread.php?t=1915459
For anyone with the A110 who's interested, and stumbled here. Feel free to give support, it will show XDA how many of us own the A110, with the hopes of a dedicated thread for us to collaborate our efforts.
heX79 said:
Update: Some better support in this thread: http://forum.xda-developers.com/showthread.php?t=1915459
For anyone with the A110 who's interested, and stumbled here. Feel free to give support, it will show XDA how many of us own the A110, with the hopes of a dedicated thread for us to collaborate our efforts.
Click to expand...
Click to collapse
OK good luck guys
Sent from my Thrive - Kuroikaze B19
pio_masaki said:
OK good luck guys
Sent from my Thrive - Kuroikaze B19
Click to expand...
Click to collapse
pio_masaki,
Did you run into "loop" files in the /dev/block when using a custom recovery, during early builds for the A100?
Something is changing the devices when the custom recovery is loading, preventing us from even mounting /cache. The devices are listed as loop1, loop2, loop3 etc. Seem familier at all?
heX79 said:
pio_masaki,
Did you run into "loop" files in the /dev/block when using a custom recovery, during early builds for the A100?
Something is changing the devices when the custom recovery is loading, preventing us from even mounting /cache. The devices are listed as loop1, loop2, loop3 etc. Seem familier at all?
Click to expand...
Click to collapse
Yeah, just get ignored so they don't show up in recovery, you'll see them in android, though.
Iirc I saw its using initramfs or wtf ever Sammy uses, which will require more work on recovery inits.
Sent from my Galaxy Nexus using Tapatalk 2
Related
Hi, sorry for the crappy english but i want to know if the "white lock" image in the google boot screen of the galaxy nexus is like the yellow triangle in the galaxy s2 when u changed the kernel...if thats the case theres any way u can change it and just leave the google word when u reboot the phone??
thx
pd: i already unlocked the device but i dont like that white lock pricture i would love the just have the google word.
The lock means your phone is unlocked. The only way to remove the lock is to re-lock your phone.
hi, tnx for answer, so theres no way to change that image??? there isnt like the bootanimation or something??
Nope. I'm pretty sure there is no way to change it.
Sent from my Galaxy Nexus using xda premium
El Daddy said:
Nope. I'm pretty sure there is no way to change it.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
what he said.
the lock shouldn't bother you anyway. it only appears for 1-2 seconds.
question
El Daddy said:
The lock means your phone is unlocked. The only way to remove the lock is to re-lock your phone.
Click to expand...
Click to collapse
Hey I was wondering what you mean by the phone is unlocked does the lock have to do anything with the phone being rooted, or the clockworkmod? Sorry im new to android
k.daya96 said:
Hey I was wondering what you mean by the phone is unlocked does the lock have to do anything with the phone being rooted, or the clockworkmod? Sorry im new to android
Click to expand...
Click to collapse
When you add su.zip for short of superuser.zip then you have root. The unlocking of the bootloader allows you the ability to install custom recovery and get root access after flashing superuser.
The only way would be if someone hacked and created a custom bootloader, in the process hiding the lock symbol, similar to what was done with BlackRose on the Nexus One.
That was done to change the NAND partition sizes, and since the Galaxy Nexus doesn't face the issue of small internal storage nobody is likely to be working on a custom bootloader for the GNex...
You can do this, actually.
LogoMe.
And yes, I use it, it works.
Jubakuba said:
You can do this, actually.
LogoMe.
And yes, I use it, it works.
Click to expand...
Click to collapse
Is that the only way? I wish they had a free version.
#Sent From md-. - bm and d,"b
phreshy said:
Is that the only way? I wish they had a free version.
#Sent From md-. - bm and d,"b
Click to expand...
Click to collapse
I've never tried it, but ROM Toolbox may be able to do it. (Maybe other free apps as well.)
The image is stored in the sbl partition on a GNex (see here) and although I haven't looked into it, but you should be able to do it just by editing that partition. Maybe segv11 can help out if you can't do it with ROM Toolbox or any other utility.
You can most likely change it with a file manager as stated before me but just make sure you have a correct size image check the logo me thread they have a bunch of icons already made and a transparent icon for the lock which will make it look like its not there
Sent from my Galaxy Nexus using xda app-developers app
efrant said:
I've never tried it, but ROM Toolbox may be able to do it. (Maybe other free apps as well.)
The image is stored in the sbl partition on a GNex (see here) and although I haven't looked into it, but you should be able to do it just by editing that partition. Maybe segv11 can help out if you can't do it with ROM Toolbox or any other utility.
Click to expand...
Click to collapse
I have rom toolbox, but the nexus isn't a supported device and I'm not brave enough to try it.lol Now, there's this app called "Flash Image GUI", which stated that it worked with the nexus, but it didn't when I chose an image to flash, so I don't know.
#Sent From md-. - bm and d,"b
---------- Post added at 12:13 PM ---------- Previous post was at 12:08 PM ----------
Alex1123 said:
You can most likely change it with a file manager as stated before me but just make sure you have a correct size image check the logo me thread they have a bunch of icons already made and a transparent icon for the lock which will make it look like its not there
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Where is the logo located exactly?
#Sent From md-. - bm and d,"b
Alex1123 said:
You can most likely change it with a file manager as stated before me but just make sure you have a correct size image check the logo me thread they have a bunch of icons already made and a transparent icon for the lock which will make it look like its not there
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I don't think you can change it with a file manager. You need to edit the sbl partition with a hex editor, and reflash it, or just echo the changed bytes to it.
Sent from my Galaxy Nexus using Tapatalk 2
phreshy said:
Is that the only way? I wish they had a free version.
#Sent From md-. - bm and d,"b
Click to expand...
Click to collapse
logo me is the only way right now, unless you compile a kernel and remove it yourself(fanger of bricking your device this way, if done wrong). but, logo me is worth it https://play.google.com/store/apps/details?id=aperture.ezekeel.logome
http://forum.xda-developers.com/showthread.php?t=1699657 for logo me icons i recommend you just buy logo me its much simpler to use that and its nice what you can do with it but honestly ive only used it a few times lol still i like supporting the developer and dont even think about cracking it lol
Off topic remark, but come on. You have a $300 phone. You can't spare 2.50?
If I could, I would, which is why I asked. At the moment I am not able to purchase anything from the market. I know many others in the same situation. So, yes, it does kind of suck, that it can't be changed for free, like the rest of the other android devices, but whatever.
#Sent From md-. - bm and d,"b
phreshy said:
If I could, I would, which is why I asked. At the moment I am not able to purchase anything from the market. I know many others in the same situation. So, yes, it does kind of suck, that it can't be changed for free, like the rest of the other android devices, but whatever.
#Sent From md-. - bm and d,"b
Click to expand...
Click to collapse
ezekeel spent a lot of time figuring out how to do it on the gnex with ics and jelly bean, it appears that its not so easy to do like in earlier android versions. with a higher chance of bricking your device. i spent a few weeks testing this mod/app for him before its initial release. for the effort and time that he put into it, he deserves to charge for it. even though i had free access to it, i bought it anyways to support his work. now the other android devices its free because there is little work that goes into it(and a completely different way then on the gnex), unlike on the gnex which is a bit more difficult to do.so far, only ezekeel has figured out how to do it.
simms22 said:
logo me is the only way right now, unless you compile a kernel and remove it yourself(fanger of bricking your device this way, if done wrong). but, logo me is worth it https://play.google.com/store/apps/details?id=aperture.ezekeel.logome
Click to expand...
Click to collapse
It's not part of the kernel though...
OP: If I get a chance tomorrow I'll see what I can find out as far as doing it without an app.
Sent from my Galaxy Nexus using Tapatalk 2
Well recently I wanted to COMPLETELY redo my XOOM in anticipation of the Jelly Bean update. I've been around Android for awhile now so it was something I'm accustomed to doing and I didn't think it would be a problem. To make a long story short, I did have a big problem and realized there wasn't really one easy, simple, automated way (with comprehensive instructions) to get a XOOM back to its factory state. I tried to solve this a little bit by making a ZIP package to return a XOOM to stock.
Here's a quick rundown:
-ONLY works for wingray (US XOOM WiFi-only/MZ604)
-Works coming from any ROM, etc. as long as your bootloader is unlocked
-Flashes the original factory software that the XOOM ran (yes that's right, Honeycomb)
-Works on Windows or Linux
-Will relock your bootloader and therefore wipe your data - this gets you COMPLETELY back to stock, folks!
There is a more comprehensive list of information and step-by-step instructions in a readme file found within the ZIP (named README.txt). READ IT before doing anything!
Once you do this it will only take 15-20 minutes to run through all the OTAs if you're looking to upgrade to the latest stock ROM. Hope this helps some people out!
DOWNLOAD HERE: http://www.mediafire.com/?etw97xdi5x1fhf2
Forgot to mention, thanks to Motorola for providing the stock images and Google for the fastboot software!
If you guys have questions, comments, requests, etc. feel free to post them of course!
Thank you very much for posting it! I am about to sell my Xoom and wanted to deliver it stock.
I was just wondering if anyone has tested it as well.
Thanks again!!
I always backup boot and system right after an OTA (need to flash CWM recovery first) - and before applying root.
Prior to taking a subsequent OTA, restore those partitions and let it fully boot - this will overwrite recovery to stock.
Sent from my Xoom using XDA Premium HD app
Thanks!
In order to get it working I had to reorder the flashing of system and recovery (system first, then recovery), else I got an error.
Flashed it on my Mac by the way. The shell script didn't work out of the box for some reason, but executing the commands in the file with the "./" part skipped and the mentioned reordering it worked flawlessly.
Going to try this later.
Sent from my Xoom using Xparent Cyan Tapatalk 2
i have done all the steps.. but the least i have push down volume and i don't know i have lock my bootloader or not.. can anybody help me? i think i have unlocked yet!
Any chance...
.. Hi, any chance you still have this file? I've been trying to put my Xoom back to stock version to sell on, but have been unable to find the needed files.
Thanks (hopefully)
For MZ601
For owner of Xoom MZ601 Umts Everest to return in one shoot to original stock ICS 4.0.4.
Download this tool: https://www.dropbox.com/s/qrazfho7p4oz4an/RSDLite 5.4.4.rar?dl=0
Download this ROM stock untouched: https://www.dropbox.com/s/8jr8zgiuc...FR_P025_A021_M007_HWumts_everest_1FF.rar?dl=0
Install RDS on your Desktop, start in administrator.
Start you tab with power + volum up. connect with the USB cable
Unzip the ROM to obtain the .sbf file
search the place of the .sbf file downloaded with RDS
push Start to flash the TAB and after few minutes you are in original last update I.C.S 4.0.4
Work coming from any ROM and any type of partition Normal or Big.
Anyone have this file for the Wingray
Sent from my Xoom using XDA Premium HD app
dkahs23 said:
Anyone have this file for the Wingray
Sent from my Xoom using XDA Premium HD app
Click to expand...
Click to collapse
You can try this. I believe it's the original Honeycomb that came with the Xoom when it was first released. I say I believe it is because it's been a long time since I've been on stock and I'm not really sure if this is ICS or Honeycomb.But, I did a bit of searching though before posting this and from what I can find, the wifi only version of the Xoom was released in Feb of 2011. If you drill down through the zip and check the properties of the files, you'll see the date modified is March 10, 2011. So, I have to assume it's Honeycomb. If you want to give it a try, I uploaded it to my dropbox. Here's a link to the file. https://dl.dropboxusercontent.com/u/67672751/MZ604_HWI69.zip
Sorry I can't be sure on this but it's been a long time since I downloaded it. I have things organized pretty good though and it's definitely for the wifi only xoom. I can tell you that.
hello can anyone can upload the everest stock version? thank you!!!
haldaios said:
hello can anyone can upload the everest stock version? thank you!!!
Click to expand...
Click to collapse
There appears to be a Wingray version in post #10. Do you need cellular capability? If not the Wingray version may work for you.
brewer75 said:
There appears to be a Wingray version in post #10. Do you need cellular capability? If not the Wingray version may work for you.
Click to expand...
Click to collapse
its ok I find it through an older post my version!! thank you for replying!!
OP's file missing
Can someone upload OP's original attachment? Mediafire seems to have taken it down.
OK
johneflik said:
You want everest European or international or USA or Korean... Be specific then chose the server you want me to upload on it
Click to expand...
Click to collapse
it doesn't matter anymore, I appear to have screwed the pooch on my Xoom. It won't wipe partitions or let me load the system partitions back on. Thanks for the offer though.
johneflik said:
You want everest European or international or USA or Korean... Be specific then chose the server you want me to upload on it
Click to expand...
Click to collapse
I want the everest version!
Sent from my SM-G920F using XDA-Developers mobile app
OK
johneflik said:
Ok here is everest but chose the version you need
International
https://drive.google.com/file/d/0ByGtxlrI5GAoOTgwdE5HSWZTcGM/view
Europe
https://drive.google.com/file/d/0B5-sw2BpNffdNm4tdU9fcHFPbUE/view
Korea
https://drive.google.com/file/d/0ByGtxlrI5GAoemhiQkNmQU9jODg/view
Good luck ... if you find difficults in downloading i might upload the one you like on other server
By the way have sold my xoom
Click to expand...
Click to collapse
Download requires permission. Please give adequate permission for download.
OK
Hi Guys,
I managed to hard-brick my phone somehow. I sent it back to HTC already, but I just don't want to do it again. Can anyone figure out what did I do wrong?
Here is the story:
1, I've rooted the phone. I tried with the one-click root first, it did not work, but the other method involving unlocking the bootloader through htcdev.com and flashing CWM (endeavoru) and SuperSU worked.
2, I wanted to install my cmdsp update, which worked already in several devices (Nexus S, Galaxy Nexus, Nexus 7, Galaxy S III). I flashed the exact version which was in the thread (that one is created from the Galaxy Nexus CM9 distro (maguro)).
3, The device booted, but then got frozen on the UI. I hesitated what to do next.
4, I thought that maguro is not binary compatible with my device, so I downloaded CM10 from this thread, extracted the necessary files and created an update.zip for this device, then flashed it.
5, It got flashed nicely, but then the phone did not boot anymore.
It had 100% battery before, but long-pressing power button did not do anything. No way to get into hboot mode, and the device is not recognized as an USB device if plugged into a mac (sorry, no windows at home). The led does not even light up if I plug it to the charger.
So, the question is: what did I do so wrong that it got hard-bricked. I might get another device from HTC, I might need to pay for that, I don't know, but I do not want to repeat this mistake.
Do not flash other phone's **** into ur phone..
No human can take horse's penis in ass
Same way phone doesn't take other phone's **** into own..
Sent from my HTC One X using Tapatalk 2
sumeshd said:
Do not flash other phone's **** into ur phone..
No human can take horse's penis in ass
Same way phone doesn't take other phone's **** into own..
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
This is an update.zip, I flashed it to many other ARM-based device with no problem (ICS, JB).
Because you don't read and experiment, that's why.
Laurentius26 said:
Because you don't read and experiment, that's why.
Click to expand...
Click to collapse
Don't read what? The doc of the update.zip that I made myself? This update.zip installs some libs into the /system partition. What can go wrong about it?
You got the SAME responses on the SAME thread you started in the at&t, rogers, telestra One XL forum. Tho your story didnt add up over there. Looks like u just need to come to terms with it amigo:beer:
#2 - CRAP Flashing doesnt pay
dlux.hu said:
This is an update.zip, I flashed it to many other ARM-based device with no problem (ICS, JB).
Click to expand...
Click to collapse
Almost every Android has an ARM architecture CPU, doesn't mean you can flash whatever you want onto every phone.
Sent from my HTC One X using xda app-developers app
Because you overwrote your hboot when flashing the device?
Try running the JB Firmware Flasher.
Sent from my HTC One X using xda app-developers app
Actually I'm very interrested in what you flashed exactly?
With a S-ON device it should not be possible to flash anything that will hard-brick your device. So maybe you could post it for me?
EDIT: The ZIP you are linking to in your other thread could never have hard-bricked your phone. On a S-ON device it is impossible to flash onto a protected partition. So something else must have happened!
It is indeed possible to hard rbick an son device only by simply flashing a rom and boot.img meant for your device.
Recently it happened in the one x community when an (anonymous) developer released a rom and several people got bricked because of it.
Sent from my One X using xda premium
TToivanen said:
It is indeed possible to hard rbick an son device only by simply flashing a rom and boot.img meant for your device.
Recently it happened in the one x community when an (anonymous) developer released a rom and several people got bricked because of it.
Sent from my One X using xda premium
Click to expand...
Click to collapse
There is no boot.img in the ZIP he links to, only libraries and an APK file. I highly doubt that could hard-brick a S-ON device, but who knows.
After a hard day of extra testing, we're proud to announce Nvflash for TF300.
This release allows unlocked devices to create a set of device-specific files that lets you access nvflash.
Once the procedure is done, you will always be able to recover any software brick (even bootloader!) as long as you keep your files safe!
NOTE:
THIS REQUIRES A NON-BRICKED AND UNLOCKED DEVICE. IT WON'T WORK ON ALREADY BRICKED DEVICES
THIS ONLY WORKS IF YOU HAVE A PRE-JB BOOTLOADER
More details at http://androidroot.mobi/?p=480
Important note: License: Due to the nature of wheelie and the importance of people always using the latest version, Wheelie is NOT redistributable! You are allowed to download it and use it, but you are not allowed to redistribute it in any way - this means no GUI's including it, no reposting zips/tar.gz's and similar! At a later date, we will be releasing our source code and relicense it as GPL.
Enjoy
- AndroidRoot.Mobi Team
Members: rayman, lilstevie, kmdm, Bumble-Bee (XDA: apache14), IEF (XDA: IEFtm)
NOTE: If anyone wishes to donate, http://androidroot.mobi/donations/ is place to do it! DO NOT DONATE DIRECTLY TO ME.
Nice, I'll have to give this try. Its good to have a safety net.
So once I have generated the files and have NvFlash working, would I be able to then flash the new JB from Asus and then use the NvFlash files to go back to ICS bootloader?
PS: This thread should be pinned.
wideopn11 said:
Nice, I'll have to give this try. Its good to have a safety net.
So once I have generated the files and have NvFlash working, would I be able to then flash the new JB from Asus and then use the NvFlash files to go back to ICS bootloader?
PS: This thread should be pinned.
Click to expand...
Click to collapse
Yes! Once you have these files, you can move back and forth between any rom/bootloader you desire. ASUS can do nothing to prevent it once you have the files for your device!
It also essentially makes your device brick proof (assuming you carefully follow our guide and do the backups!), so development gets a lot more safe
Yyyeeeeeahhhhh
THIS IS AWESOME!! Thank you guys so much for all your hard work.
I followed the process as explained in the guide and everything went perfectly.
For anyone there still on the fence... give it a go! The whole process takes 2-3 minutes. Just make sure you don't skip any step of the process and keep your generated files in 3 or 4 different locations (thumbdrive, cloud, external HD and the TF300 in my case).
Kudos to all of you again!
Now I am really pissed that I took the JB updated
Gold job
Envoyé depuis mon LT18i
Even working perfectly on the TF300TG(!) used windows 7 x64 for the whole process...
There are any hopes working nvflash for JB BOOTLOADER? Or is it impossible?
rayman said:
[*]THIS ONLY WORKS IF YOU HAVE A PRE-JB BOOTLOADER
[/LIST]
[/COLOR][/SIZE][/B]
Click to expand...
Click to collapse
What do you mean with Pre-JB bootloader?
You mean OTA JB from ASUS?
w0uter said:
What do you mean with Pre-JB bootloader?
You mean OTA JB from ASUS?
Click to expand...
Click to collapse
Yes
Sent from my Nexus S 4G using Tapatalk 2
w0uter said:
What do you mean with Pre-JB bootloader?
You mean OTA JB from ASUS?
Click to expand...
Click to collapse
You need to be on ICS Bootloader...so yes,if you updated to Jelly Bean using the OTA or the official rom from Asus site you CAN'T use this.
Pretoriano80 said:
You need to be on ICS Bootloader...so yes,if you updated to Jelly Bean using the OTA or the official rom from Asus site you CAN'T use this.
Click to expand...
Click to collapse
Please don't abuse me because I may have missed any pertinent discussion but is there any thing in the works to eventually develop this to be workable with the JB Kernels and mods? :fingers-crossed:
I would guess there will be a way to downgrade and at this point you will be fine
Sent from my ASUS Transformer Pad TF300TG using xda app-developers app
Sorted in APX mode and installing drivers now!
Sweet backed up all files to Laptop/Tablet/Drive/Dropbox!
Not sure how to use NVFlash but at least I know its there if required!
I followed all the steps to the letter (I think) because everything worked up to and included generated the 5 files (blob.bin, blob.log, bootloader.ebt, create.bct, recovery.bct) which I saved to like 4 places lol, but I can't seem to get into APX mode. When ever I hold volume up and power I just end up in CWM recovery. Am I missing something?
wideopn11 said:
I followed all the steps to the letter (I think) because everything worked up to and included generated the 5 files (blob.bin, blob.log, bootloader.ebt, create.bct, recovery.bct) which I saved to like 4 places lol, but I can't seem to get into APX mode. When ever I hold volume up and power I just end up in CWM recovery. Am I missing something?
Click to expand...
Click to collapse
Yeah just reboot the tablet and hold VOL + and it will go into APX mode
Northern-Loop said:
Yeah just reboot the tablet and hold VOL + and it will go into APX mode
Click to expand...
Click to collapse
Ok thanks that worked. Now I am in APX mode, which driver do I point it at? It's not finding the driver automatically.
Edit: nevermind I had the driver, just needed to point to the right folder to install it. #facepalm
wideopn11 said:
Ok thanks that worked. Now I am in APX mode, which driver do I point it at? It's not finding the driver automatically.
Click to expand...
Click to collapse
Its on the guide main page http://forum.xda-developers.com/showthread.php?t=1426502
Awesome! Thanks for all the help. Is there some info on how to use NvFlash with these shiny new backups?
I can't use this - already on jb, but still wanted to extend thanks. I'm sure this is a gem to many. Well done devs.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Has anyone read about Dirty Cow yet?
http://www.xda-developers.com/9-yea...-dirty-cow-can-root-every-version-of-android/
I read over on the V20 forums that one developer was able to get it to root his Note 7 that he refused to return. Surely it can work on the Note 5!?
jellybear456 said:
Has anyone read about Dirty Cow yet?
http://www.xda-developers.com/9-yea...-dirty-cow-can-root-every-version-of-android/
I read over on the V20 forums that one developer was able to get it to root his Note 7 that he refused to return. Surely it can work on the Note 5!?
Click to expand...
Click to collapse
I've said earlier if someone could compile it for me I would give it a try, I am no developer so I really don't know what I'm doing when I comes to that but I know enough to find my way through cmd an adb
Surely since no one has written a reply someone must be working on this, I'm pretty techy but I am in no way shape or form a dev but I am down to help, test or give input where I can.
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
dpwguenther said:
I've said earlier if someone could compile it for me I would give it a try, I am no developer so I really don't know what I'm doing when I comes to that but I know enough to find my way through cmd an adb
Click to expand...
Click to collapse
Message me good sir.
Also the biggest problem is SELINUX is set in bootloader.
Now that it's been proven drammer can flip the memory on the note 5 (tested myself with their test app) we should be able to set SELinux to passive with the right knowhow and then root with dirty cow.
Unfortunately I am not a dev nor do I know how to code android but this all looks promising. Hopefully all the devs haven't moved on from this device (like I'm sure most of us will when our contracts are up).
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
Jspex said:
Now that it's been proven drammer can flip the memory on the note 5 (tested myself with their test app) we should be able to set SELinux to passive with the right knowhow and then root with dirty cow.
Unfortunately I am not a dev nor do I know how to code android but this all looks promising. Hopefully all the devs haven't moved on from this device (like I'm sure most of us will when our contracts are up).
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
Click to expand...
Click to collapse
We can already set SELINUX to permissive. The problem is the bootloader sets the kernel to enforcing on everyboot.
TechNyne66 said:
We can already set SELINUX to permissive. The problem is the bootloader sets the kernel to enforcing on everyboot.
Click to expand...
Click to collapse
We cannot set SELINUX in MM..? All the dirtyc0w scripts work fine to get run-as or farm on system of the phone as long as you compile with arm64-v8a. But SELINUX makes dirtyc0w completely useless when trying to drop to root shell...
straby187 said:
We cannot set SELINUX in MM..? All the dirtyc0w scripts work fine to get run-as or farm on system of the phone as long as you compile with arm64-v8a. But SELINUX makes dirtyc0w completely useless when trying to drop to root shell...
Click to expand...
Click to collapse
We can't do anything with MM. I can try to compile whatever if you can get me the files.
If you are still on lollipop with eng kernel tether root. Can you try to pull boot pull boot and recovery
http://forum.xda-developers.com/general/security/farm-root-recovery-image-pulling-t3490089
I can already flash boot and recovery but the att crap that no one seams to understand WILL lock the phone out untill you do a full odin. However maybe some way can work as we haven't tried all but a simple flash of custom recovery to the recovery portion will not work.
What about rowhammer
TechNyne66 said:
I can already flash boot and recovery but the att crap that no one seams to understand WILL lock the phone out untill you do a full odin. However maybe some way can work as we haven't tried all but a simple flash of custom recovery to the recovery portion will not work.
Click to expand...
Click to collapse
i was asking if you could pull the original recovery from the phone, not flash it. I just wanted to get a look at it...
straby187 said:
i was asking if you could pull the original recovery from the phone, not flash it. I just wanted to get a look at it...
Click to expand...
Click to collapse
Yes we already have stock recovery. If you want to message me in the morning I can send it to you.
how is it looking for this new method, I feel like we are really close.
killernos said:
how is it looking for this new method, I feel like we are really close.
Click to expand...
Click to collapse
I can't get a single thing to work. Seams like KEXEC is out best bet and we need to focus all efforts on this. All we need is a custom kernel with kexec support and I can test to see if it will load. I have tried and tried for hours on hours to get a kernel to compile with no success.
I'm new here. Some may know who I am some may not. I just got my note 5 last week after my v10 took a ****......what's kexec and what's the error when compiling
Sent from my SAMSUNG-SM-N920A using Tapatalk
MysteryEmotionz said:
I'm new here. Some may know who I am some may not. I just got my note 5 last week after my v10 took a ****......what's kexec and what's the error when compiling
Click to expand...
Click to collapse
If you have to ask then compiling a kernel is probably beyond your experience (it's well beyond mine and I work in I T )
dezborders said:
If you have to ask then compiling a kernel is probably beyond your experience (it's well beyond mine and I work in I T )
Click to expand...
Click to collapse
You know what your right. I'm just go back into the shadows and continue boot to help. A quick search on xda would have shown you in plenty capable.
PS...When compiling a kernel it normally gives you some kinds of error message so you know where to start lookin
Sent from my SAMSUNG-SM-N920A using Tapatalk
MysteryEmotionz said:
You know what your right. I'm just go back into the shadows and continue boot to help. A quick search on xda would have shown you in plenty capable.
PS...When compiling a kernel it normally gives you some kinds of error message so you know where to start lookin
Click to expand...
Click to collapse
My bad lol no offence intended