[Q] [WIP] Volume track skip - Galaxy Note II Q&A, Help & Troubleshooting

Hey guys,
Loving the note 2 even with stock. But i really miss the long press volume track skip.
So i started to follow this guide to make one for the n2:
http://forum.xda-developers.com/showthread.php?t=1728236
Fairly quickly i noticed this was made for HTC devices. But i worked on comparing code and find correct params and switches.
But eventually i got stuck (At the part "invoke-virtual/range {p0 .. p0}, Lcom/android/internal/policy/impl/PhoneWindowManager;->isMusicActive()Z")
The function does exists however samsung doesn't use it at all.
I have never used smali before, and working off assembly knowledge.
I am hoping that somebody might be able to help, Or has a smali for samsung devices which i could compare to.
I will attach a unmodified (from stock note2), modified HTC and my WIP of the PhoneWindowManager.smali
Thanks

I just finished a test version of this mod.
However since i don't have CWM i am not sure how to proceed.
Can i flash just one file with Odin? And if the mod fails it will boot loop, can i still push a file through Odin?
(android.policy in this case)
If this is not possible then i guess ill just have to flash CWM

Related

How to install NFSFAN's custom Roms

Hi i was wondering if there was anyone out there who was kind enough to explain in detail how to install this Rom because by the looks of the pictures and the reviews, it is a great Rom. OH and if there is an answer to this already, please direct me to it because i have searched for hours and cannot find anything.
Thanks in advance
How far is your knowledge when it comes to custom ROMs? Do you have your phone unlocked?
If your phone isn't unlocked, go here:http://forum.ppcgeeks.com/showthread.php?t=20370
I could use a little help to. My phone is unlocked and I have flashed another rom before but when I download the rom file I can't do anything with it. I seem to remember using another program to handle the rom file before flashing but I have looked and looked and have come up empty handed. Someone pointing in the right direction would be great.
Basically I am stuck between getting the file on the computer and starting to flash. I can get my phone to the color screen and all.
Terms you should know before-hand, haha:
-The color RGB color screen is called the Bootloader mode (you get to it by holding the power button + camera button, and sticking you stylus in the slot at the bottom of you phone to reset.)
-Hard-reseting: Flashing the phone to default state of the flashed ROM. (Hold talk key + end call key, and sticking you stylus in the slot at the bottom of you phone to reset.)
-Soft-reseting: Simply restarting your phone. (Sticking you stylus in the slot at the bottom of you phone to reset.)
-------------------------------------------------------------------------
0. Unlock Phone. (http://forum.ppcgeeks.com/showthread.php?t=20370)
1. Go in to Boot-loader mode. (Text towards the bottom of the screen
should read "Serial" if you phone isn't connected to the PC.)
2. Connect phone to PC. ("Serial" text should change to "USB")
3. Extract the files from .rar file you download. (Use Winrar.)
4. Run ROMUpdateUtility.exe and follow the on screen instructions.
- Your phone will start showing a progress bar when the flashing starts.
- Once done, the phone will restart. (Should reset and windows should boot, but still do step 5.)
5. Hard-reset the phone.
6. Dance in place.
-------------------------------------------------------------------------
*pants* Hope that helps!
Stickfigure, thanks a bunch for your summary of the ROM loading process! My Sprint Touch has been giving me lots of problems (freezing on incoming calls, data connection stops working randomly, phone not wanting to get out of roam and back into EV mode, and many many more). Needless to say, it is frustrating and I want to throw it at a wall. I'm sure my reset button is going to fail since I've poked it so many times.
Anyways, I've been wanting to install a custom ROM and finally have the chance during my spring break from classes, but I wasn't quite sure how to do it. Your post definitely helps.
One more question...is the process basically the same if I want to install a different custom ROM? If you know of any other tutorial or noob info pages that might help me I'd appreciate it too.
Thanks again!
Stickfigure, thanks for the instructions. Winrar was the piece that I was missing. Once I installed that I had the new rom installed the the phone was working fine in a bout 15 minutes.
hapa_dude said:
Stickfigure, thanks a bunch for your summary of the ROM loading process! My Sprint Touch has been giving me lots of problems (freezing on incoming calls, data connection stops working randomly, phone not wanting to get out of roam and back into EV mode, and many many more). Needless to say, it is frustrating and I want to throw it at a wall. I'm sure my reset button is going to fail since I've poked it so many times.
Anyways, I've been wanting to install a custom ROM and finally have the chance during my spring break from classes, but I wasn't quite sure how to do it. Your post definitely helps.
One more question...is the process basically the same if I want to install a different custom ROM? If you know of any other tutorial or noob info pages that might help me I'd appreciate it too.
Thanks again!
Click to expand...
Click to collapse
There are some great tutorials out there for beginners, one of the best of which is Dharvey's "UPDATED- CONSOLIDATED Rev A./GPS TUTORIAL" found on PPCGeeks; it is no longer available for some reason, but you may be able to find a repost somewhere.
Thanx
Thankx every one who contributed to this thread because it really helped.

ClockWorkMod for Sprint Galaxy Tabs

PREPARATION STEP! download sgs kernel flasher from the market (must be rooted I believe) and do a kernel backup as this process changes your kernel.
SPRINT TAB INSTRUCTIONS THAT WORKEDFOR MANY SPRINT TAB OWNERS. IT MAY NOT WORK FOR YOU!
Ok here it is, Thank koushs for this product, cruiserbax for his awesome instructions and Benjamin Dobell for giving up Heimdall flashing utility and install instructions.
I NOR THE ANYONE LIST ABOVE ARE RESPONSIBLE FOR THIS NOT WORKING!!! OR ANY DAMAGE IT MAY DO TO YOUR TAB!!
To get the zip file containing the zimage download it from here. http://www.megaupload.com/?d=SV6IKL1D
To flash the zimage you will need to use Heimdall which can be downloaded here. http://www.glassechidna.com.au/products/heimdall/ <--------click on the binaries link for 1.1.1
instruction are below.
Heimdall install instructions
1. Download Heimdall here http://www.glassechidna.com.au/products/heimdall/
2. Download Microsoft Visual C++ 2010 Redistributable Package (x86) and install it. http://www.microsoft.com/downloads/...5E-6DE6-4D3A-A423-37BF0912DB84&displaylang=en <------only if you are using Microsoft widows
2. Unzip Heimdall and you should have several files in the folder called Heimdall.exe, Heimdall-Frontend.exe, QtCore4.dll, QtGui4.dll, Readme.txt and drivers folder containing zadig.exe
3. Put you tab into Download mode(while the tab is OFF hold Volume Down + Power Button). Hook the tab up to you PC and Run Zadig.exe to install the drivers.
4. From the menu chose Options -> List All Devices.
5. From the USB Device list chose "Samsung USB Composite DEvice".
6. Press "Install Driver", click "Yes" to the prompt and if you receive
a message about being unable to verify the publisher of the driver
click "Install this driver software anyway".
7. Done. This only needs to be done once.
ClockWorkMod Install Instructions
1. First root you tab (use one click root or z4root) then downloaded rom manager.
2. Unzip the flash_image_VZW_zimage.zip. It will have have two files flash_image and zimage. you only need to use the zimage file. Open Heimdall-Frontend.exe and browse to where you unzipped the zimage to and select it. Make sure the box infront of zimage is checked. Hit start and it should flash the zimage and reboot the tab.
when it reboots it will get stuck at the samsung screen long hold the power button to shut it off. boot into recovery (cwm) power button plus volume up button it will start backing up to do the fs conversion but it will fail at /data and /cache. it will leave you in recovery.
3. While still in recovery select factory reset/data wipe when finished also do a cache wipe.
4. select reboot system, if you let it try to boot it will loop/hang on the SAMSUNG logo, this is not an issue just hold power key until it powers off.
5. while off hold volume up + power until you see the SAMSUNG logo then release both keys! NOTE: if step 4 does not fully power off and reboots just keep holding the power button until the screen blanks again then let go and quickly hold down only volume up + power until you see the SAMSUNG logo.
6. once it boots back into recovery (cwm) it will start the same backup/conversion process again, this time it will finish and leave you in recovery.
7. select reboot system and wait for it to load the tab back to froyo. (it will be back to factory defaults with the activation screen again)
8. Your tab will still be rooted so install terminal emulator and run "mount" to verify that your partitions are ext4.
9. Power off then boot back into recovery with volume up + power, it will boot back into recovery (cwm)
10. Do a backup and reboot your tab.
Source:
http://www.thegalaxytabforum.com/index.php?/topic/1775-clockworkmod-for-sprint-galaxy-tabs/
Yes, I tried this and it works great but be aware that certain kernels seem to mess it up.
Which Kernel Seems To Work The Best?
@ lloydcabraham
Which kernel is the most stable?
I rooted my tab last night in preparation for the HC port, and I'm curious about whether CWM is necessary... seems everything needs to be flashed via Heimdal or Odin, so is the advantage to having CWM installed just the wipe capabilities? I'm used to my EVO, and flashing/rooting/modding which is obviously different, I just don't understand what the differences are, I guess. THANKS SO MUCH FOR THE STEP BY STEP! Simpletons like me find them EXTREMELY useful!
Great work, and thanks again!
Sent from my PC36100 using XDA Premium App
I'll have to try this soon.
IP IHI II IL said:
I rooted my tab last night in preparation for the HC port, and I'm curious about whether CWM is necessary... seems everything needs to be flashed via Heimdal or Odin, so is the advantage to having CWM installed just the wipe capabilities? I'm used to my EVO, and flashing/rooting/modding which is obviously different, I just don't understand what the differences are, I guess. THANKS SO MUCH FOR THE STEP BY STEP! Simpletons like me find them EXTREMELY useful!
Great work, and thanks again!
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Somewhat Offtopic:
Chances are the honeycomb port will come to GSM Devices First, We can only hope that it comes to Sprint and Verizon devices.
I believe the build being worked on right now in here is based on a cdma device...
Not off topic at all. THE ONLY HC port is currently being built by spacemoose (reading more than one thread on one website helps) and that wasn't the focus of my question. Please read before you quote/insinuate. Don't wanna be tagged with the troll label...
cdguider said:
Somewhat Offtopic:
Chances are the honeycomb port will come to GSM Devices First, We can only hope that it comes to Sprint and Verizon devices.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA Premium App
Clockworkmod has many advantages if you flash different roms, or say wanted to backup your current sprint rom & settings before testing Honeycomb Port.
As far as Honeycomb Port goes,
Again Chances are Honeycomb will port to Gsm Devices First,
Honeycomb is still Closed Code.
I said somewhat off topic, which it was, considering the thread is titled Clockworkmod.
Get your facts straight.
cdguider said:
@ lloydcabraham
Which kernel is the most stable?
Click to expand...
Click to collapse
I like Bauxite but you will get a flaky camera (Sometimes won't initialize without reboot) and seems to mess up CWM (Although redoing these steps fixes it) but I do love running @ 1.4 super stable!
cdguider said:
Clockworkmod has many advantages if you flash different roms, or say wanted to backup your current sprint rom & settings before testing Honeycomb Port.
As far as Honeycomb Port goes,
Again Chances are Honeycomb will port to Gsm Devices First,
Honeycomb is still Closed Code.
I said somewhat off topic, which it was, considering the thread is titled Clockworkmod.
Get your facts straight.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=11780452&postcount=1
3/26/11 #2:...Second... The "dirty" port will be for CDMA devices, but as soon as the CDMA version is released I'll look into getting a GSM version out asap. Shouldn't be hard. Instead of using my own kernel for this one, I'm using a modified version of Boushh's kernel and can probably hack together a suitable kernel for other devices as well. My own kernel for the larger project is still in fluctuation as I have to make changes to suit the build on a regular basis, but when I finalize that kernel I'll release it as an update and it will get a repo of it's own.
Click to expand...
Click to collapse
The quote was for what?
Re-read it one more time...
Really
I still stand by my message.
It's also apparent you didn't go back to page 1 otherwise you would have known I acknowledged spacemoose1 Honeycomb Port.
Despite someone working on Honeycomb port for Sprint / CDMA devices.
Chances are someone else is working on it for GSM, as with damn near anything, GSM devices will most likely get it first,
KEYWORD: most likely, and if you read the previous post - keyword is chances are
Bottom line is who cares who gets it first.
I'm well aware of most developments going on XDA
can u guys just drop it already!
Ok im stuck I followed steps but I am stuck at the samsung screen won't boot into recovery I don't know what I did wrong... I need help I have it stuck! (sigh) uSING hEIMDALL It isn't specific on which box I should use the zimage in which box using heimdall... I used it in the recovery under other made sure the box was checked. It ran through backups 2 times then looked like it was launching into recovery cwr 3.0 but when I picked it up it turned off when I turned on all I get is the samsung logo FOREVER... I have tried using heimdall again and tried to use it under FACTORYFS but same result. Please help. All I have now is a Huge Expensive Paper Weight. HELP
*** Ok after further review *SIGH* I understand I probably should have studied the damn thing better there is an option for zImage there... So how bad did I mess this thing up and is there a way to UnDue what I have Done?
Update-
So I was able to flash the Zimage and get to recovery but when I tried to wipe/data/cache and load K-lean rom I got this ---->http://img819.imageshack.us/img819/8655/imag0061y.jpg
I was also able to boot in but couldn't launch because every one of the launchers would fc.
I will attempt another ROM but I fear it is bricked.... I don't give up easily so any help would be awesome.
Thanks in advance.
Damn,
Can you boot into recovery at all? Ifa ll fails, put your Tablet in downloader mode, and flash the file below, follow the instructions in the zip file, if you have done some of the steps skip them, however read very carefully.
http://www.gsmelite.com/Sprint Galaxy Tab EA24 Flasher Odin.zip
cdguider said:
Damn,
Can you boot into recovery at all? Ifa ll fails, put your Tablet in downloader mode, and flash the file below, follow the instructions in the zip file, if you have done some of the steps skip them, however read very carefully.
http://www.gsmelite.com/Sprint Galaxy Tab EA24 Flasher Odin.zip
Click to expand...
Click to collapse
So I was able to flash the Zimage and get to recovery but when I tried to wipe/data/cache and load K-lean rom I got this ---->http://img819.imageshack.us/img819/8655/imag0061y.jpg
I was also able to boot in but couldn't launch because every one of the launchers would fc.
I will attempt another ROM but I fear it is bricked.... I don't give up easily so any help would be awesome.
Thanks in advance.
Thanks for the link... Will give it a try.
Really don't know what to say about the error message, My tab was messed up with errors like can't mount....., some other stuff, I had to send mine in to get replaced, never would go past the samsung logo. At the time the only thing Sprint users had was the Stock DJ30 With Modem.
Now we have no modem.
EA24 Stock
Ext 4
Honeycomb Port In Progress.
cdguider said:
Damn,
Can you boot into recovery at all? Ifa ll fails, put your Tablet in downloader mode, and flash the file below, follow the instructions in the zip file, if you have done some of the steps skip them, however read very carefully.
http://www.gsmelite.com/Sprint Galaxy Tab EA24 Flasher Odin.zip
Click to expand...
Click to collapse
Before I tried that I loaded the Honeycomb ROM well it isn't but the Khasmek's AOSP beta 1 and it worked everything working but the real question is what to do now... If I reboot does it load agian? Should I use Rom manager and run a recovery Backup? what would you advise?
****Update
So after getting everything setup I tried to do a boot to recovery through Rom Manager and low and behold back to dreaded SAMSUNG screen with NUTIN happening. Will try your steps next
****Update
After following steps and flashing image with odin... I was able to boot up fine... Downside---> My Verizon tab is now a Sprint Tab ... I need to find the .tar for VZW anyone? ANYONE? *SIGH*

[SCRIPTS][Win] A100 Flashing Toolkit v1.1 7-16-12 Discontinued

As I wrote the guide I realized the files, scripts, and images are scattered through multiple threads, which makes finding what you need difficult, even from a main thread (the guide for example). This was compounded even more when I was writing the CM9 Install Guide for the CyanogenMod Wiki and listed the commands themselves, it became huge, intimidating, and looks extremely daunting, I can only imagine what a new flasher must think seeing it! And and so I decided perhaps I can fix this, and with that I present to you...
The A100 Flashing Toolkit!
What is it?
A single zip file that, when unzipped, contains EVERYTHING you need, ADB, fastboot, scripts, CWM recovery image, everything you need to take your stock ICS A100 through rooting, unlocking the bootloader, and flashing CWM recovery (twrp coming soon)!
How is it used?
Its a set of 6 PC scripts, 3 for windows users (.bat) and 3 for linux users (.sh). Run in order from the same folder, and you can just click and run, reboot, click and run, reboot, click and run, install custom rom, done!
You MUST already be on ICS! This is not for HC, if you are on HC update to ICS FIRST!
Instructions
Make sure you are on ICS! Read the bold red letters above! You have been warned! You should already have installed the Acer USB drivers for ADB to work.
Ok, now you're on ICS....right?
Download and unzip the file to whatever folder you can remember, for example c:\acer or ~/acer.
Open your file manager of choice and browse on over to where you unzipped the files, and get ready.
Windows
Right click on A100-root-win.bat and select Run as Adminitrator.
Once that is finished, let your tablet reboot.
Once it's rebooted, right click on A100-unlock-win.bat and select Run as Administrator.
Once this finishes, let the tablet reboot again (the script will tell you what's happening)
Once it's rebooted, right click on A100-recovery-win.bat and select Run as Administrator.
Allow it to finish, it'll reboot a couple times.
Half the time it reboots into recovery, other reboots into system, not sure why it happens.
If it boots into recovery, go ahead and make a full backup, might as well.
If it boots into system, reboot into recovery and make a full backup, might as well.
At this point, you can now wipe and install a custom ROM, see the A100 Guide in General for ROMs and instructions on this.
Linux
Execute A100-root-linux.sh and allow it to run.
Once that is finished, allow tablet to reboot.
Exectute A100-unlock-linux.sh and allow it to run.
Let the tablet reboot
Execute A100-recovery-linux.sh and allow it to run.
It'll either reboot into recovery, or system, it does one or the other for some reason.
If rebooted into recovery, make a full backup.
If rebooted into system, reboot into recovery and make a full backup.
Wipe and install a new custom ROM, see the A100 Guide in General for ROMs and instructions on this.
How to boot into recovery
There's a few ways, 1 way is an app like quick boot, you can use adb by typing adb reboot recovery or you can do it manually.
Power off the tablet.
Press and hold the volume - button, closest to power and lock switch.
Holding volume - press and hold Power.
Hold until the screen says Booting recovery kernel then let go.
You should be in recovery, either CWM, TWRP, or stock, whatever you have installed.
As always I am open to suggestions, advice, or reports! Feel free to post up or PM me with any issues, questions, bugs, or ideas!
Download
A100 Flash Toolkit 1.1 7-16-12
Now featuring the correct bootloader!
Thanks to smokku for pointing this out.
Who do we thank for this package?
ZeroNull: Alot of the scripting is based on his work, and borrows his ADB and fastboot executables.
ptesmoke: Uses his CWM recovery.img file
CyanogenMod Iconia Team: For allowing me the chance to write for the Wiki, and realizing this NEEDED to be done.
Anyone else I'm forgetting, I'm sorry I will add you as soon as I remember (feel free to drop me a note!)
Sounds great, many thanks.
Thanks for all you hard work and patience.
a100 flash program
After several hours trying, having trouble with some of the batch files. Appears some file names called in .bat different than actual file names, also had to invoke adb from Command prompt window, wouldn't work from windows file manager. Followed instructions but process is breaking down in second batch file. After correcting file names, batch file runs but recovery.img is failing. Need help figuring this out.
Esat
Birbey said:
After several hours trying, having trouble with some of the batch files. Appears some file names called in .bat different than actual file names, also had to invoke adb from Command prompt window, wouldn't work from windows file manager. Followed instructions but process is breaking down in second batch file. After correcting file names, batch file runs but recovery.img is failing. Need help figuring this out.
Esat
Click to expand...
Click to collapse
Oh wow OK I'll take a look I must have mixed everything up. My desktop is littered with files from all these projects. I'm sorry about that I should have double checked everything before I uploaded it. If the called files are different then the scripts it must be the old version mixed with new scripts or something. I should have it squared away sometime tonight/tomorrow morning.
Edit: I'm assuming by saying command prompt you use windows, the a100-root-win.bat file looks fine, was this one giving any issues?
I'm checking the second and third now for whatever is going on.
Tapatalked from my Galaxy S II.
Fixed.
I'm not able to unlock my a100, when it enters boot loader and I press volume - and + nothing happens, any advice? Thanks a lot.
Sent from my A100 using XDA
diegof18 said:
I'm not able to unlock my a100, when it enters boot loader and I press volume - and + nothing happens, any advice? Thanks a lot.
Sent from my A100 using XDA
Click to expand...
Click to collapse
You have to be FAST when it gets there, it times out in like half a second it seems.
When you run it, have the tab in your hand, fingers on volume - and volume + (volume - is next to the lock switch). As soon as you see the screen change, hit volume - then volume +. It takes a few tries usually. It'll just sit there until you reboot afterwards.
Hi, I was wondering, since I just rooted yesterday (got this tab last friday) should I skip the script for rooting and simply run the other two or do I have to run the root script anyways? by the way Im having some real weak reception from this tablet, like 2 bars only and thats when standing about 5 feet from the router, Im willing to follow this procedure in order to try one of the custom roms to see if the wifi weak signal goes away (Ive tried most of the things there are to attemp to fix this, including messing around with my router) do you know if any one has successfully fixed this with a custom rom? if so which one? thanks in advance and sorry for (kinda) hiijacking the thread.
elander said:
Hi, I was wondering, since I just rooted yesterday (got this tab last friday) should I skip the script for rooting and simply run the other two or do I have to run the root script anyways? by the way Im having some real weak reception from this tablet, like 2 bars only and thats when standing about 5 feet from the router, Im willing to follow this procedure in order to try one of the custom roms to see if the wifi weak signal goes away (Ive tried most of the things there are to attemp to fix this, including messing around with my router) do you know if any one has successfully fixed this with a custom rom? if so which one? thanks in advance and sorry for (kinda) hiijacking the thread.
Click to expand...
Click to collapse
Congrats on the purchase and welcome! You can skip over rooting if you already have rooted ICS. Not HC.
The weak wifi is pretty common, mine is weaker then any other devices I have, usually by a bar or 2. Custom roms won't fix it, I think they just have the power turned down on it. Its also possible there is a bad connection to the antenna internally. If you're very unhappy stop Modding now and return to stock and exchange for another unit or brand.
Any other questions feel free to ask.
Tapatalked from my Galaxy S II.
thanks for the info.
pio_masaki said:
Congrats on the purchase and welcome! You can skip over rooting if you already have rooted ICS. Not HC.
The weak wifi is pretty common, mine is weaker then any other devices I have, usually by a bar or 2. Custom roms won't fix it, I think they just have the power turned down on it. Its also possible there is a bad connection to the antenna internally. If you're very unhappy stop Modding now and return to stock and exchange for another unit or brand.
Any other questions feel free to ask.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
thanks for your fast reply, I was contemplating the idea of flashing some custom rom as a last resort before either opening up the tab's case to check for myself that everything was "wired right" as Im not too happy with the idea of sending this off to acer's as I live in the Dominican Republic and I'd hate to pay the overpriced shipping fee if it is something that I can fix by myself, but on the other hand I might as well break something new instead of fixing the wifi anthena, so I guess I'll have to claim the warranty and hope the wont send me another faulty unit (I've read somewhere some people had issues with the replacement units). Such a great little device cursed with bad QA. anyways, if I hard reset the tab it'll be back to stock right? (as of now the tab is running stock os with root access and the modified wpa_wifi apliance to gain access to adhoc networks) Thanks
elander said:
thanks for your fast reply, I was contemplating the idea of flashing some custom rom as a last resort before either opening up the tab's case to check for myself that everything was "wired right" as Im not too happy with the idea of sending this off to acer's as I live in the Dominican Republic and I'd hate to pay the overpriced shipping fee if it is something that I can fix by myself, but on the other hand I might as well break something new instead of fixing the wifi anthena, so I guess I'll have to claim the warranty and hope the wont send me another faulty unit (I've read somewhere some people had issues with the replacement units). Such a great little device cursed with bad QA. anyways, if I hard reset the tab it'll be back to stock right? (as of now the tab is running stock os with root access and the modified wpa_wifi apliance to gain access to adhoc networks) Thanks
Click to expand...
Click to collapse
I'm not sure, but I don't think resetting these puts them back to 100% if rooted, the root stays since it sits in /system. You'll have to manually remove SU then reset to get rid of the root, I think. Other option is restore through the update.zip method which should wipe /system. You could try a hard reset and see if it removes SU or not, it might.
Does the unlock script only works with the pre-release of ICS?
I cant get to the unlock mode... allways saying "xxxx .11 ics fast boot xxxxxxx"
NeO_CooL said:
Does the unlock script only works with the pre-release of ICS?
I cant get to the unlock mode... allways saying "xxxx .11 ics fast boot xxxxxxx"
Click to expand...
Click to collapse
Not quite clear on what you're asking, but as far as I know it should work on any version bootloader unless they changed it on some update, which wouldn't surprise me.
What is the whole message, and when is it occuring?
I have the latest ICS version availble thru OTA.
Or i´m not being fast enough?
Already tried a million times the Volume - and Volume +.
Guetting this message:
"Bootloader V0.03.11-ICS Starting fastboot usb download protocol"
Should get the unlocked mode right?
NeO_CooL said:
I have the latest ICS version availble thru OTA.
Or i´m not being fast enough?
Already tried a million times the Volume - and Volume +.
Guetting this message:
"Bootloader V0.03.11-ICS Starting fastboot usb download protocol"
Should get the unlocked mode right?
Click to expand...
Click to collapse
Ok if you don't get the new screen with two icons, then it isn't unlocking yet. It seems the script is hanging before passing the next step.
When it gets to that screen again, type
fastboot oem unlock
as soon as you hit enter, get ready for that volume down then up, so maybe have it in your lap with your fingers on the volume rocker.
I'll look at the script again to see why it's hanging, or if it isn't hanging, why it's shooting past that point without waiting.
Forgot to say i´m using the windows version.
Thanks
pio_masaki said:
Ok if you don't get the new screen with two icons, then it isn't unlocking yet. It seems the script is hanging before passing the next step.
When it gets to that screen again, type
fastboot oem unlock
as soon as you hit enter, get ready for that volume down then up, so maybe have it in your lap with your fingers on the volume rocker.
I'll look at the script again to see why it's hanging, or if it isn't hanging, why it's shooting past that point without waiting.
Click to expand...
Click to collapse
The issue is that you included the A100 bootloader in the archive with a script to write it.
A100 bootloader (version 0.03.11-ICS) is not unlockable.
You need to write A200 bootloader (version 0.03.06-ICS) to your device, to have the unlocking option.
You know you have unlockable bootloader when you see green ACER logo in the bottom-right side of the screen instead white one in the center.
The script and blob you included is used to restore the original A100 (not unlockable) bootloader.
For the ones looking for the unlockable bootloader, it's here: http://forum.xda-developers.com/showthread.php?t=1557445
smokku said:
The issue is that you included the A100 bootloader in the archive with a script to write it.
A100 bootloader (version 0.03.11-ICS) is not unlockable.
You need to write A200 bootloader (version 0.03.06-ICS) to your device, to have the unlocking option.
You know you have unlockable bootloader when you see green ACER logo in the bottom-right side of the screen instead white one in the center.
The script and blob you included is used to restore the original A100 not unlockable bootloader.
For the ones looking for the unlockable bootloader, it's here: http://forum.xda-developers.com/showthread.php?t=1557445
Click to expand...
Click to collapse
It's just labeled a100, it isn't the actual a100 blob. But go ahead and use that link until I get the chance to go back through it, I'm obviously messing it all up somewhere, I may have used the a100 blob and gotten it mixed up with the a200 blob when I was renaming and shifting things around. I'll pull the download for now until I get the chance to get it all sorted out, sorry guys.
Edit OK its back up with the proper boot loader for unlocking. I can't believe I did that. Huge thanks to smokku for pointing that out!
No worries.
And yeah, you have to be quick when it asks to toggle unlock, like half a second quick.

Devs - Please replace your atmel_maxtouch.c with this one

Hello all,
First I want to express my appreciation for those who take the time to make ROMs for our TF201/300T tablets. Doing just this little task took 3 days of experimenting, I couldn't imagine debugging an entire ROM!
As some of you may know, people with broken touchscreens are getting replacements on eBay that are the wrong version, and are having reverse x-axis issues. The only way this was solved previously was to install Hairybean 2.31 which had the corrected driver and init script to activate it on the install. Unfortunately that meant that we with the wrong screens were stuck on Android 4.2, and what fun is that?
I have figured out and created a new driver for the atmel_maxtouch which will allow you to turn on the reverse axis by echoing 1 to /sys/module/atmel_maxtouch/parameters/reverse_axis. For those without the reverse axis issue, you should be fine, as the reverse axis is only called by the command above.
There's a lot of great ROMs out there, and now those with the different screens can enjoy them too, and all you need is this driver and an init.d script.
Please let me know if you have any questions or need something debugged (though I am not a programmer, so how much I may be able to help will be limited ). The new atmel_maxtouch.c is attached in the zip.
I've added it to KatKernel #19 that will be in the next KatKiss V18
Hi. I have an Asus TF300T with touchscreen issue. It doesn't working even if I replaced it. Maybe the replaced part was the wrong one... Can I do anything? I have JB 4.2.1 with the latest bootloader, root, bootloader unlocked. I flash via fastboot the TWRP recovery but I can't flash or use it because it is only touch usable...so I can't flash Katkiss rom... What can I do?
ADB is active...

KINDLE FIREHD 8.9. TWRP unable to read/load rom error Help Please

Hi guys n Gals How you all doing? Staying safe i hope!! Im posting this incase it is of any use to anyone who happens to stumble upon an old tablet as i did, But is absolutely bamboozled with what to do next.
Well then i had been looking for help on this issue with regard to Kindle Jem and done my fair share of reading before signing up here.
I am right out of the wrapper and wet behind the ears with Kindles and the like(1st time rooting anything at all) however i managed to install TWRP 2.8.6.0 on su rooted kindle using the bin4ry method.
I followed step by step a tutorial on Youtube named " KindleFireHD89 to pure android"
1. At first i was getting read/load errors:
when attempting to flash cm10.1 cm11/12 through adb sideload i was getting the error message "unable to read cm 11/12" or "unable to load cm11/12" each time i try to flash the rom.
So I done some research on XDA and found a thread to do with the \LARGEADDRESS issue , so downloaded the program to use more than 2GB ram for the flash process, all to no avail. (THIS WAS ABSOLUTELY NO USE AT ALL)
I soon figured i was copying and pasting the commands for flash/fastboot wrong ( i was forgetting to add .img to the name of the image files i was pasting into the command prompt to flash lol)
2. I done a bit of reading around and saw that most , if not all the files were severely obsolete (like the Jem) so i searched around and first upgraded to TWRP 3.0.0.2 from 2.8.6.0 which i feel made a big difference if not just for a smoother gui alone.
3. As my determination and curiosity got the better of me i began replacing the roms also , flashing newer ones each time in this order:
cm 10.1 (success)
cm 11(success)
cm 12.1 (success)
And finally onto Lineage OS 14.1 along with GApps 7.1 Pico where i remain , however i am unable to fix the bluetooth issue as i dont know the commands/ paths or method to alter the LTE file replacement. (any help with this would be great guys or girls (i know Ladye made a fix i think) i just dont know how to go about editing these files.
I got into the menu brand new , though weirdly it wasnt by the volume up button, it was by turning on/off about 5 times and then holding the POWER button in and finally the TWRP Recovery screen would popup.
### edited### i know this is an old kiindle hence why there is no replies .....
####23rd May 2020 EDITED YET AGAIN ##### So i wondered whether there was a recent newish kinda Rom for the JEM after managing to flash (with great difficulty and beginners syndrome) custom rom in TWRP 3.0.0.2.
As i said earlier this was a kindle that was found and when i got it in out the rain and dried off with the hairdrier treatment , was amazed it still worked. So i figured it was a tough mofo and deserved to live outwith the bin since he made it this far.
Anyway when i checked it out the firehd 8.9 was blacklisted ((((Which i am assuming will mean i at least dont need to worry about disabling OTA updates??????))))
So bottom line and after all the fuss above trying to root etc i got 14.1 lineage os without the bluetooth but ill figure that out soon.
For anyone out there this post may help if you can be bothered to read through it haha.
###Last but not least I would like to thank all the guys n gals who make these mods possible and xda themselves for not binning these old posts for noobs like myself . Respect people . thanks again man ###

Categories

Resources