Related
I thought it might be useful to put all the info into one thread.
I hope it's completely needless to say that I don't take any credit, since I haven't contributed anything to make that possible
This guide is for rooting your CURRENTLY installed firmware, flashing custom roms, or if you want to upgrade to Gingerbread
If you are NOT S-OFF yet, you either need to get / use an XTC Clip, or use a software exploit / hack (AlpharevX).
The basic differences between both approaches are the following:
AlpharevX:
"Software" S-OFF using an exploit
Bootloader S-OFF
It will flash a hacked HBOOT that sets your device S-OFF.
If you flash an unmodified RUU, or anything that replaces this HBOOT, you will lose S-OFF
-> Not a problem if you stay with custom roms!
Completely free and great solution!
XTC Clip:
Complete "hardware" S-OFF
All locks removed including sim and cid lock.
Permanent solution (radio S-OFF)
-> You can flash anything and won't lose S-OFF
Costs money, or you need to find someone that owns a Clip to do this for you
UPDATE:
Hawkysoft posted about a rare occurrence that has been reported after using AlpharevX:
If you get a security warning in hboot, you will need an XTC Clip to get you running again!
Of course you might also send your phone to repair, but you'll most likely need to pay for that.
So if you experience this problem, either get someone with an XTC Clip to help you out, or buy an "XTC Clip Pay as you go", which is a very cheap variant that comes only with one use (rechargeable) and costs around 30USD.
See the following tutorial to set your device S-OFF with AlpharevX: GUIDE -> S-OFF
And pause at the point where you should install CWMR (ClockworkMod Recovery) to consider the following options:
Do you want to switch to a custom rom after S-OFF?
-> continue with the guide above installing CWMR
Do you want to keep your official firmware and replace your official recovery with CWMR?
--> continue with the guide above installing CWMR,
but before you install a custom rom, make a backup of your current firmware in CWMR!
Do you want to keep your orig firmware AND the official recovery?
--> don't continue with the guide above and follow this guide instead
Be it Froyo or Gingerbread doesn't matter.
If you insist you only want to root your Froyo rom and not upgrade to Gingerbread immediately, please scroll further down.
A rooted Froyo rom is NOT necessary for flashing and afterwards rooting Gingerbread!
If you need further details about flashing custom roms just scroll down.
If you haven't done so already (you didn't get an OTA or you didn't do it manually yet) and you want to upgrade to Gingerbread, here's a short guide on how to flash it first..
How to install the Gingerbread update
download one of the Gingerbread Roms
http://forum.xda-developers.com/showthread.php?t=1033922
This link is for the Incredible S only of course, but the following works also for the Desire S, but then please use a rom for your phone
ATTENTION: If you are NOT S-OFF yet and you are planning to using AlpharevX, you MUST use an ruu compatible with AlpharevX! Check that first!
start the RUU installer
[*]go into your tmp folder to get rom.zip from the extracted files of the RUU installer:
Access the tmp folder by clicking on start/run and put %tmp% into the textbox. Or for windows 7 put this into this search textbox in the "start menu"
Look for the most recent folder (sort by date). In that folder look for rom.zip or simply do a search.
After acquiring rom.zip from your tmp folder you can exit the RUU installer
[*]Put rom.zip onto your sdcard and name it PG32IMG.zip.
boot into the bootloader.. (press and hold vol.down + press power) it will automatically start to install it and ask you if you want to proceed.
After a reboot remove PG32IMG.zip from your sdcard (otherwise it would ask you to reinstall the update each time you boot into the bootloader)
use morelocales2 from the market if you need additional languages
finished. Now follow the steps below for rooting the fw
Guide below partly out of date!
It works, but there are easier methods available now.Work in progress
What you need if you want to root your Gingerbread rom:
an incredible S / Desire S that is S-OFF
Gingerbreak OR SuperOneClick newest version
Busybox
UPDATE:
Some users reported that they weren't able to root using SuperOneClick or Gingerbreak.apk no matter what they tried.
After I reflashed my IS I also run into problems. Although it's not unusual that it doesn't work the 1st time, I decided to do it manually.
I have attached a zip with all the files needed and a script that you could try which does everything for you.
It doesn't do any magic or different than SuperOneClick, but if you do it this way you get to see what's actually happening and if it fails and where / why.
When using this you also don't need to reboot between the tries, reinserting / remounting your sdcard is sufficient.
Please report any bugs.
How to use:
make sure usb debugging is enabled
make a backup of your sdcard's content or use another fat32 formatted sdcard where you don't care to possibly lose its content.
download the zip file: View attachment 596033
extract the zip and open a shell/command prompt and change into that directoy
on Linux start runexploit.sh, on Windows start runexploit.cmd
if Gingerbreak doesn't finish and you ONLY get to see lots of "sendmsg() failed?" without any other messages in between, you should try any of the following options:
hit ctrl + c to abort, unmount / remount your sdcard and start over. It could take a few tries
Doublecheese reported it took him 8-9x
WHILE Gingerbreak is running and printing "sendmsg() failed?" forever, pull and take out your SDcard completely and reinsert it
this worked well for vontdeux, jkolner and me
Thanks to Vontdeux, Doublecheese, jkolner and everyone else afterwards for the feedback!
now, after you see '#', you can hit ctrl + c or close the shell
run root.sh on Linux or root.cmd on Windows from the same directory. This will install su, SuperUser.apk and busybox
when it's finished you're done and have root
then it's very recommended to get "rom manager" from the market, open it and install clockworkmod recovery for installing custom roms, backing up your system et.c.
Files:
Big thanks to Chainfire for GingerBreak and CLShortFuse for SuperOneClick!
SuperOneClick: http://forum.xda-developers.com/showthread.php?t=803682
OR Gingerbreak: get the latest version here: http://forum.xda-developers.com/showthread.php?t=1044765
Busybox installer: https://market.android.com/details?id=stericson.busybox
Steps:
make sure usb debugging is enabled
make a backup of your sdcard's content or use another fat32 formatted sdcard where you don't care to possibly lose its content.
use the latest SuperOneClick which might be easier.
start the application and select "GingerBreak" as exploit.
But respect the info and warning of the creator of the Gingerbreak.apk:
Chainfire said:
WARNING: Apparently on some devices the root exploit causes the SD card (internal or external) to be formatted. Also, if it gets stuck but you do see the card mounting/unmounting, try formatting your SD card yourself and try again (or use a different SD card) often this works (a fix for both issues is being looked at)
Click to expand...
Click to collapse
click root check Chainfire's post if you run into problems (also with SuperOneClick because it uses his exploit): http://forum.xda-developers.com/showthread.php?p=13086954#post13086954
after it's finished your phone will reboot and you're essentially done.
Alternatively, don't use SuperOneClick but follow the guide of Chainfire from the beginning to install Gingerbreak on your device and root your phone: http://forum.xda-developers.com/showthread.php?p=13086954#post13086954
(optional) get the busybox installer mentioned above, start the application and install/update your busybox installation.
(optional, but highly recommended) Now for the ultimate pleasure get Rom Manager from the market and use it to install a "custom recovery": ClockWorkMod Recovery
What you need if you want to root your Froyo rom:
an Incredible S / Desire S that is S-OFF
SuperOneClick newest version
(optional, but highly recommended) Busybox installer app
Files:
Update: apparently the current SuperUser app is crashing for some users.
If you experience these problems see the next section
Big thanks to CLShortFuse for SuperOneClick!
SuperOneClick:: http://forum.xda-developers.com/showthread.php?t=803682
Busybox installer: https://market.android.com/details?id=stericson.busybox
Steps:
use the latest SuperOneClick
start the application and select "psneuter" as exploit.
click root
after it's finished you might need to reboot for getting Superuser app to pop up when needed.
(optional) get the busybox installer mentioned above, start the application and install/update your busybox installation.
(optional, but highly recommended) Now for the ultimate pleasure get Rom Manager from the market and use it to install a "custom recovery": ClockWorkMod Recovery
So how to flash custom roms?:
it's extremely easy
put your favorite custom rom onto your sdcard
install rom manager if you haven't done so already
open rom manager and click "install ClockworkMod Recovery
next click "install rom from sdcard"
select your custom rom you put on your sdcard
select to backup your currently installed rom just in case you want to revert back
Most of the time you also need to check wipe cache and data (follow the instructions of the creator of that custom rom to find out if you need to do that or not. If you wipe your data, all your current settings will be lost however so make a backup!)
wiping Dalvik Cache is always a good idea and won't harm your settings
after pressing ok, Rom manager will boot into Recovery, backup your current rom (if you told it to), wipe (if you told it to), install the custom rom and reboot
Solution for SuperUser crashing:
All thanks go to rmk40 who patched SuperUser for us running newer versions of Sense:
http://forum.xda-developers.com/showthread.php?t=886999
rmk40 said:
The latest official build of Superuser does not work with newer Sense ROMs (such as Vision 1.72+, anything released recently). HTC has started utilizing a relatively new feature of sqlite; a journaling mode called WAL (write-ahead logging). It's actually smart. WAL journaling should improve sqlite throughput, which represents a large amount of Android's IO and benefits applications across the board. The downside is it broke Superuser because it's actually special in its' use of sqlite.
Click to expand...
Click to collapse
How to install the patched version
Update 5/14: Fixed a serious bug in the replace_su script that made it pretty much useless
If you didn't root your phone yet
You might want to patch SuperOneClick before using it the first time.
Either download the patched su and SuperUser.apk, or just use the already patched version of SuperOneClick attached to this post. View attachment 591017
If you already rooted your phone:
Usually the first app requesting root access does work with the unpatched version, so you can use this to gain root access on the shell to replace SuperUser and su with the patched versions. If SuperUser doesn't pop up, open Superuser and remove all apps you already whitelisted for su access and try again
To keep it simple, I have attached an archive with a script to do this for you: View attachment 595753
make sure USB Debugging is enabled (in settings/apps/development)
extract replace_su.zip on your windows or linux pc
open a terminal and change into that directory
on windows run replace_su.cmd, on linux run replace_su.sh
the script needs root access so you need to press allow when SuperUser pops up on the phone
If you already installed a custom recovery and want to do it that way:
Just download rmk40's flashable zip: http://forum.xda-developers.com/showthread.php?t=886999
put it onto your sdcard
reboot into recovery by starting rom manager and selecting reboot into recovery
if this doesn't work because SuperUser fc, shutdown your phone completely (fast boot disabled in settings/power). Press and hold vol-down and press power. From the bootloader menu: select "recovery"
use ClockworkMod to flash the zip. "install/flash zip from sdcard.."
you can also just replace those files (SuperUser.apk and su) in your SuperOneClick directory and then re-run SuperOneClick.
Here's the "patched" SuperOneClick View attachment 591017
Update 5/14: Fixed an error in the replace_su script.
Update 5/10: updated because of a request to re-add the Froyo rooting info
Update 5/09: updated because of SuperUser crashing issue
Update 4/27: updated due to new version of SuperOneClick now supporting Gingerbreak
Update 4/26: updated because of Gingerbreak, which makes this much shorter and easier. Thanks very much Chainfire for all the hard work!
Update 4/24: thanks very much to Hawkysoft for pointing out that psneuter doesn't work for Gingerbread and further instructions)
So if you are already gingerbreaded, please scroll down
Update 4/23: OFFICIAL CLOCKWORKMOD RECOVERY NOW AVAILABLE!!
Big thanks to Koush and Hawkysoft!
Hawkysoft said:
time has arrived, after supplying all the info, koush did a hell of a job with creating this
download rommanager from the market
and install the recovery for the Incredible S
WARNING DO NOT PARTITION SDCARD <- THIS WILL BRICK YOUR DEVICE, A FIX IS ON THE WAY
all thanks go out to koush offcourse
i tested:
backup, whipe data, restore, reboot... all worked
bugs found:
sdcard > if you do parition this, you will end up jtaggin your device cuz its bricked! (the fix is on the way)
backup time > in the folder it shows a wrong time that it has been created atleast for me it does.. it shows a 3 hour difference idk how its set but its not a big deal in my opinion
Click to expand...
Click to collapse
Please check the post by Hawkysoft!
http://forum.xda-developers.com/showthread.php?t=1046759
Nice, thanks!
OTA Updates
TimMun said:
Nice, thanks!
Click to expand...
Click to collapse
Thanks for the thanks
NP
Does anyone know if your phone would still get OTA Updates after doing it this way?
I guess so, but then of course you would need to repeat those steps after you installed an official update.
madmaxx82 said:
Thanks for the thanks
NP
Does anyone know if your phone would still get OTA Updates after doing it this way?
I guess so, but then of course you would need to repeat those steps after you installed an official update.
Click to expand...
Click to collapse
I don't know the answer to this question but first I would like to actually see an update
TimMun said:
I don't know the answer to this question but first I would like to actually see an update
Click to expand...
Click to collapse
Haha, it was really funny coincidence. After I s-offed the phone I got an OTA
BTW: If anyone wants to be S-OFF and doesn't mind visiting me in Austria, I'd help you out. For free of course
well if u use stock rom and rooted that one, you will get notified that there is an update, but im not totaly sure if it installs (especially when u use custom recovery, than its a nogo)
timbo007up said:
well if u use stock rom and rooted that one, you will get notified that there is an update, but im not totaly sure if it installs (especially when u use custom recovery, than its a nogo)
Click to expand...
Click to collapse
Thanks, so if it doesn't work you'd need to reflash the original recovery first..
If you do it you will fail and end flashin a standard rom with hboot xD
Been there.... Better first update than flash the recovery or you will be busy for a few ^^
Sent from my HTC Incredible S using XDA Premium App
Hawkysoft said:
If you do it you will fail and end flashin a standard rom with hboot xD
Been there.... Better first update than flash the recovery or you will be busy for a few ^^
Sent from my HTC Incredible S using XDA Premium App
Click to expand...
Click to collapse
Ahh thanks for the warning
Since the custom recovery is installed already anyway when there's an OTA update available, wouldn't the following work?
If I get notified about an available OTA update, I could flash a complete RUU, then get the OTA and afterwards re root + reflash the custom recovery?
Newbies question: if you just want root in order to use i.e. titanium I suppose you don't need to install PG32IMG right?
Sent from my HTC Incredible S using XDA App
nikant said:
Newbies question: if you just want root in order to use i.e. titanium I suppose you don't need to install PG32IMG right?
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
Correct. Its only needed to flash custom roms.
Sorry for newb question... What does S-OFF mean?
Read the rooting topic in the dev section,
But to make it easy for you: S-OFF means Security Off.
Which allows us to (over)write system files
timbo007up said:
Correct. Its only needed to flash custom roms.
Click to expand...
Click to collapse
And nandroid Can't live without it... of course especially if you flash custom roms, but also if you don't, titanium is just not always 10.000% enough
There is another recovery available from GOAPK with Reboot function that works.
can you confirm that it fully works with backin up and restoring?
since the current one failes at restoring
;p
testing it...
first try to backup FAIL <- Error while generating md5 sum!
second time as well this is a major failing recovery
I am going to try porting clockwork myself from scratch tonight
Sent from my HTC Incredible S using Tapatalk
With this recovery in the first post, I had an error at the time of restoration, with the one I posted, an error of md5 sum, but with the tutorial as an attachment, the worries of md5 sum is adjusted by 5 minutes
So I can now restore quietly after each crash, as I try to adapt a framework-res.apk to my Incredible S
Just at it now
creating md5 sums failed.. restore of course also failes..
I just restored a previously created backup with the one from llnhhy successfully
So we have a recovery that has all the functions, but has trouble creating md5 sum, and another that did not have the reboot function with a problem of restore, by mixing the two should do it .. .
Amazon Stock OS for Kindle Fire HD 8.9 - Version 8.4.3
BEFORE YOU BEGIN MAKE SURE YOU HAVE A 2ND-BOOTLOADER INSTALLED CORRECTLY AND CAN SEE THE BLUE LOGO DURING BOOTUP:
http://forum.xda-developers.com/showthread.php?t=2128175
This flash .zip file contains the Amazon OS 8.4.3 update + root/Superuser.apk and should have OTAs disabled. You can use this to revert back to the Amazon OS should you need to for any reason.
NOTE FOR LTE USERS: This does *NOT* contain the wankit update for LTE modem firmware.
Download Information for OS 8.4.3:
Mirror 1: http://goo.im/devs/Hashcode/jem/kfhd8-amazon-os-8.4.3.zip
md5sum: d67ab5cd944dbf9d9509b44aa1d4a7e3
Download Information for OS 8.4.1:
http://d-h.st/VnR
md5sum: a39c815becf8517729c2baec2ad13582
OLDER VERSIONS:
Download Information for OS 8.3.1:
http://goo.im/devs/Hashcode/jem/kfhd8-amazon-os-8.3.1.zip
md5sum: 6a2584c9a52d9d57dc13e64e05558985
Download Information for OS 8.3.0:
http://goo.im/devs/Hashcode/jem/kfhd8-amazon-os-8.3.0.zip
md5sum: 9394219ae608bb73b292fcbb84d48aa2
Download Information for OS 8.1.4:
http://goo.im/devs/Hashcode/jem/kfhd8-amazon-os-8.1.4.zip
md5sum: c9e87973e42d6b34f8269469f9fb479a
INSTALLATION (TO REVERT TO AMAZON OS):
Place flash .zip file onto your SD card
Reboot into recovery
Wipe system
Use "INSTALL" and find the .zip file (NOTE: CM10.1 may create a "0" directory under /data/media so you may need to navigation up to /data/media and back down to find .zip)
Make sure to WIPE CACHE if you're currently on stock (and do a full FACTORY RESET for wiping data/cache if you're on CM10.1 going to this).
Reboot
Go back through the stock Amazon setup process
Works flawlessly thank you Hashcode!!
Works great - but not without a 'heart attack moment' first time around.
I pushed the kfhd8-amazon...zip to the /sdcard/download folder from a Windows box. It was put into /sdcard/0/download.
Once in TWRP, I naviguessed to the /download folder to install the old software - and the folder was blank (apparently TWRP defaulted to the /sdcard/download folder). Ok...Hashcode warned us about the duplicate folders in JellyBean, so I backed out of 'install' and used to file manager to find the kfhd8-ama...zip in the /sdcard/0/download folder. It was an easy click to select it to copy, then navigate to the 'other' download folder, then press paste. FAILED I tried again and that copy failed as well.
Navigating back to the 'install' menu refreshed the screen and the update software zip was magically there. Maybe the failed copy didn't really fail? Maybe the initial read of the /download folder failed and needed to be refreshed? Dunno.
But the flash worked perfectly. And it's apparently resilient enough to catch newb errors - I was so happy that the software appeared that I forgot to wipe the system again after installation. Pressing reboot to the system resulted in an attempted boot and a return to TWRP where I could give the system a good wipe. The next boot was normal.
Whew.
Does TWRP backup of CM10 work as other normal phones or we also need to take care of the "stack" file? because I saw these lines in the update-script. Will a backup/restore of CM10 overwrite this?
---------
run_program("/sbin/sh", "-c", "rm -f /tmp/stack; for i in $(seq 1024) ; do echo -ne '\\x00\\x50\\x7c\\x80' >>/tmp/stack ; done");
run_program("/sbin/dd", "if=/tmp/stack", "of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system", "bs=6519488", "seek=1", "conv=notrunc");
---------
thanks, will try this later...
stock room problem
Hello I opened this post: http://forum.xda-developers.com/showthread.php?p=38337627#post38337627
What can I do to solve. Thank you
Re: [ROM-STOCK] Amazon OS 8.1.4 (Flash .zip for TWRP)
field3d said:
Hello I opened this post: http://forum.xda-developers.com/showthread.php?p=38337627#post38337627
What can I do to solve. Thank you
Click to expand...
Click to collapse
You can start by following the instructions given to you in that thread and directing all non-development related questions to the Q&A forum.
Sent from my KFJWI using Tapatalk 2
I just flashed back to this until the CM built has working sound. I'm not sure if this is already known, but if you flash a ICS based gapps package on top of this you have all the gapps =D
vln004 said:
I just flashed back to this until the CM built has working sound. I'm not sure if this is already known, but if you flash a ICS based gapps package on top of this you have all the gapps =D
Click to expand...
Click to collapse
Seriously? And everything works? I already have everything installed but if this is true that would make going back and forth between cm and Amazon really easy
wojo797 said:
Seriously? And everything works? I already have everything installed but if this is true that would make going back and forth between cm and Amazon really easy
Click to expand...
Click to collapse
Only had about 30 minutes to play with it before going to bed. But everything that i tested worked fine. Google play installs apps fine, youtube works as expected, installed a couple other apps and everything works as it should.
vln004 said:
Only had about 30 minutes to play with it before going to bed. But everything that i tested worked fine. Google play installs apps fine, youtube works as expected, installed a couple other apps and everything works as it should.
Click to expand...
Click to collapse
So I bought a demo unit Kindle Fire HD 8.9 (you know, the ones in the store with just a demo OS installed) and I should have it by next week. When I root it I can install this ROM and everything works (sound, camera, HDMI etc.) just like a full one bought in the store?
OP updated for a new 8.3.0 stock ROM .zip file to flash in TWRP.
It includes the new kernel + stock ROM, but NOT the wankit update for LTE users.
Hashcode said:
OP updated for a new 8.3.0 stock ROM .zip file to flash in TWRP.
It includes the new kernel + stock ROM, but NOT the wankit update for LTE users.
Click to expand...
Click to collapse
Just install? Or wipe cache and dalvik? Thanks for doing all this work.. Very much appreciated
If you are on stock, then you can just install this over the top of 8.1.4. If you've been playtesting CM10.1 you will need to wipe data/cache.
Re: [ROM-STOCK] Amazon OS 8.3.0 (Flash .zip for TWRP) [04/02 - Version 8.3.0]
Hi,
Is it possible install flash plugin to use with DolphinHD? I ask this because i use Kindle to see NBA games from Game Time.
Sent from my Incredible S using xda premium
Running stock rooted so I simply installed this update over top..no cache or dalvik wipe. After reboot the play store kept force closing.went back into recovery and wiped cache and dalvik. Play store no longer force closing.maybe just isolated to me but I would wipe caches
wojo797 said:
Running stock rooted so I simply installed this update over top..no cache or dalvik wipe. After reboot the play store kept force closing.went back into recovery and wiped cache and dalvik. Play store no longer force closing.maybe just isolated to me but I would wipe caches
Click to expand...
Click to collapse
Good point. Adding wipe cache to the OP.
Wow, this is great, with 8.3.0!!
But I never succeeded downloading the file as everytime it stopped at 30%-70%. Anyone can help?
Finally I managed to download it through a proxy.
I am new to rooting and tablets. I cannot understand how to load "flash in TWRP". I try running adb commands in CMD but it says it is a unrecognized command. Can someone make this idiot proof? I am doing something wrong and I don't want to brick my kindle hd 8.9
Deodexed, debloated stok rom with supersu, busybox, xposed framework and updated minimal google apps.
Flash this rom with custom TWRP recovery FOR LOLLIPOP -> http://forum.xda-developers.com/grand-prime/development/custom-recovery-twrp-2-8-7-0for-lollipop-t3190351
Make sure you follow all the steps correctly:
1. download all files and put them on SD Card
2. boot into TWRP recovery
3. do a complete wipe (system, data, cache, internal storage)
4. first flash only G530fz_502_deodex_xposed.zip
5. when finished on the same screen WIPE CACHE
6. reboot to system and wait for rom to boot up, IT WILL LAST 10 MINUTES maybe more, it is normal for deodexed roms
7. once the language menu shows up you can reboot to recovery again
8. this time DO NOT wipe just flash xposed-v65-sdk21-arm-arter97-V5-generic[1].zip
9. DO NOT wipe cache and reboot to system
10. this time system boots faster but apps will be updated
11. when you complete setup first update SU binary in superuser app
12. install XposedInstaller_3.0_alpha4[1].apk and reboot
13. open Xposed app it should say framework is connected
14. optionally make a backup and enjoy your phone
DOWNLOAD G530FZ deodexed xposed rom
SCREENSHOTS (rom has stock settings and launcher. screenshots might look little different as I use dpi 220, navbar in build.prop and action launcher on my phone..)
If you like this, you can buy me a beer, thanks!
____
Base rom is http://www.sammobile.com/firmwares/download/54047/G530FZXXU1BOG2_G530FZOXA1BOG2_PHE/
Credits:
twrp recovery http://forum.xda-developers.com/grand-prime/development/custom-recovery-twrp-2-8-7-0for-lollipop-t3190351
xposed lollipop http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3113463
deodexer - http://forum.xda-developers.com/android/software-hacking/script-app-joeldroid-lollipop-batch-t2980857
how to deodex - http://forum.xda-developers.com/sprint-galaxy-s5/general/how-to-deodex-lollipop-rom-t3065596
justarchi kitchen - https://github.com/JustArchi/ArchiKitchen
stericson -busybox
chainfire -supersu
If you are wondering what modules work, I attached wanam module for lollipop.
For status bar modding use http://repo.xposed.info/module/com.bocharov.xposed.fsbi, xstana isn't fully compatible with stock samsung lollipop roms.
Can i flash this rom on my galaxy grand prime model g530H...?
great jop >>> hope that it moded for g530h
Nasir javed said:
Can i flash this rom on my galaxy grand prime model g530H...?
Click to expand...
Click to collapse
zshou92 said:
great jop >>> hope that it moded for g530h
Click to expand...
Click to collapse
I don't think it will work, I will try to make rom for G530H later.
I just need these files from g530h running stock 5.0.2 rom and TWRP recovery:
/cache/recovery/last_log
and all files from these folders:
/system/app
/system/priv-app
/system/framework
also version number of stock rom that the phone is running or link to download from sammobile / samsung-updates sites
These files must be pulled with adb or file manager, I need files from rom that is in use, if I extract files from stock odin tar it might not work.
If someone can send me these files I will make you deodexed rom. :good:
hangy18 said:
I don't think it will work, I will try to make rom for G530H later.
I just need these files from g530h running stock 5.0.2 rom and TWRP recovery:
/cache/recovery/last_log
and all files from these folders:
/system/app
/system/priv-app
/system/framework
also version number of stock rom that the phone is running or link to download from sammobile / samsung-updates sites
These files must be pulled with adb or file manager, I need files from rom that is in use, if I extract files from stock odin tar it might not work.
If someone can send me these files I will make you deodexed rom. :good:
Click to expand...
Click to collapse
here's the last_log
http://www.datafilehost.com/d/35178a46
rom base
http://www.sammobile.com/firmwares/download/53879/G530HXCU1BOH3_G530HSER1BOH3_SER/
the apk's
http://www.mediafire.com/?d35x0z8187cch0r
pull from adb :
Thank you very much !!!
i'll try this night
Edit: Thank you it works perfectly on my G530FZ.
working well on my g530fz
What apps are removed? But great. Finaly some development for this phone!
pajocos said:
What apps are removed? But great. Finaly some development for this phone!
Click to expand...
Click to collapse
All Google apps except Google play, galaxy apps market and knox apps since it was disabled
pajocos said:
What apps are removed? But great. Finaly some development for this phone!
Click to expand...
Click to collapse
Pd.Chal said:
here's the last_log
http://www.datafilehost.com/d/35178a46
rom base
http://www.sammobile.com/firmwares/download/53879/G530HXCU1BOH3_G530HSER1BOH3_SER/
the apk's
http://www.mediafire.com/?d35x0z8187cch0r
pull from adb :
Click to expand...
Click to collapse
Thanks I will make rom for g530h during the weekend.
weather widget is missing. Is it suposed? I'm looking in system.rar that you uploaded but still didn't find him
Unfortunately nothing works for me
Probably it is caused by encrypted storage in my case but flashing TWRP via Odin leads to boot into black screen with coloured vertical strips but nothing else....flashing back PhilZ CWM works but using it for installation of this ROM doesn't work (as expected)...
So, what do you suggest? Flashing back Stock ROM (v4.4.4) and trying it again or is there anyone else with the same issues but with unencrypted phone?
Thx for your help,
x.
waiting for the 530H
Good day!
Let's make this happen! How can i help? I have G530H with XXU baseband.
Sent from my SM-G530H using XDA Free mobile app
ZenitramXdaDev said:
Let's make this happen! How can i help? I have G530H with XXU baseband.
Sent from my SM-G530H using XDA Free mobile app
Click to expand...
Click to collapse
http://forum.xda-developers.com/grand-prime/development/mini-rom-deodex-apps-lollipop-5-0-2-t3194189 another user made it already
pajocos said:
weather widget is missing. Is it suposed? I'm looking in system.rar that you uploaded but still didn't find him
Click to expand...
Click to collapse
I may have deleted some more apps, there you go:
https://mega.nz/#!RVFDWDSD!_jTpUTYE5h9t07WGPphWoUTXIj-Z0fmv5YRnlxF5p94
i deleted the weather app
xkovi said:
Unfortunately nothing works for me
So, what do you suggest? Flashing back Stock ROM (v4.4.4) and trying it again or is there anyone else with the same issues but with unencrypted phone?
Click to expand...
Click to collapse
I don't have any knowledge of encryption in android, try searching xda forums for more advice, but I think such features were designed to be used with stock system and recovery. Also samsung KNOX is disabled in this rom but I am not sure if it affects device encryption in any way.
Pd.Chal said:
here's the last_log
http://www.datafilehost.com/d/35178a46
rom base
http://www.sammobile.com/firmwares/download/53879/G530HXCU1BOH3_G530HSER1BOH3_SER/
the apk's
http://www.mediafire.com/?d35x0z8187cch0r
pull from adb :
Click to expand...
Click to collapse
Hi, is this rom working http://forum.xda-developers.com/grand-prime/development/mini-rom-deodex-apps-lollipop-5-0-2-t3194189 ?
I am not sure if version for g530h is still needed.
Let me know.
Thanks
This patcher is now outdated. Use the new SuperSU instead. http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
This zip is a systemless version. That means that you'll get root and be able to use it normally, but your system partition will not be modified, like in normal root methods. Only for Marshmallow.
Keep reading for disadvantages and advantages
Chainfire had released a newer version of his SuperSU that doesn't need to modify the system partition to provide root access. This method doesn't have much of a practical application right now, but it allows you to flash OTA updates without having to unroot or flash the stock system partition.
HOW TO USE:
If you have rooted before, flash the system partition (or reinstall the ROM) before flashing this zip.
Download the attached zip, and flash it from a recovery (I tested it with TWRP).
Download SuperSU 2.56 from here: http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 (Just download the apk)
Reboot to TWRP. If it asks you whether you want system to be mounted as r/w, and if you want to take OTAs later, choose to keep system read-only (this will replace TWRP with stock recovery on reboot).
Flash SuperSU-v2.56-20151030013730.zip
Reboot
TWRP will say that you are not rooted, just ignore that. Do not tell it to root it.
This will work with all Marshmallow kernels, even the stock kernel.
Drawback : A factory data reset will remove superuser privileges. If that happens, simply flash SuperSU-v2.56-20151030013730.zip again.
TO RECEIVE OTA UPDATES :
Just make sure not to do anything that modifies /system. For example, no build.prop changes, and no system app removal. Or even if you do these, make sure to undo these changes before flashing an OTA. You can flash OTAs without unrooting now.
Flash the stock boot.img for your current Android version before flashing OTAs.
BUGS :
I didn't find any, yet, but Chainfire wrote the following on his thread:
Apps with hardcoded paths to su (seriously?) will bork
Factory reset unroots
Factory reset wipes pin
...
Bugs... Bugs everywhere!
ADDITIONAL INFO :
This zip will replace sepolicy as mentioned on Chainfire's thread (thanks to @metaspook for the patched sepolicy, which I extracted from his zip), so you'll be able to get root access even on SELinux enforcing kernels (only the stock MM kernels right now). Also, you can flash any other kernel (as long as it comes in a zip format, not as an img) before or after flashing this, and you'll still have root access.
out386 said:
Chainfire had released a newer version of his SuperSU that doesn't need to modify the system partition to provide root access. This method doesn't have much of a practical application right now, but it allows you to flash OTA updates without having to unroot or flash the stock system partition.
HOW TO USE:
Download the attached zip, and flash it from a recovery (I tested it with TWRP).
Download SuperSU 2.56 (or newer, if it supports systemless mode) from here: http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 (Just download the apk)
Flash SuperSU-v2.56-20151030013730.zip
Reboot
This will work with all Marshmallow kernels, even the stock kernel.
Drawback : A factory data reset will remove superuser privileges. If that happens, simply flash SuperSU-v2.56-20151030013730.zip again.
TO RECEIVE OTA UPDATES :
Just make sure not to do anything that modifies /system. For example, no build.prop changes, and no system app removal. Or even if you do these, make sure to undo these changes before flashing an OTA. You can flash OTAs without unrooting now.
Flash the stock boot.img for your current Android version before flashing OTAs.
BUGS :
I didn't find any, yet, but Chainfire wrote the following on his thread:
Apps with hardcoded paths to su (seriously?) will bork
Factory reset unroots
Factory reset wipes pin
...
Bugs... Bugs everywhere!
ADDITIONAL INFO :
This zip will replace sepolicy as mentioned on Chainfire's thread (thanks to @metaspook for the patched sepolicy, which I extracted from his zip), so you'll be able to get root access even on SELinux enforcing kernels (only the stock MM kernels right now). Also, you can flash any other kernel (as long as it comes in a zip format, not as an img) before or after flashing this, and you'll still have root access.
Click to expand...
Click to collapse
Well done bro!
I'm just waiting for this
Help regarding installation
I am using MicroMax Android One with Marshmallow
Currently, I've not tired the phone.
When I open recovery, I see some options like Apply update from SD card, mount, cache wipe, factory reset, etc.
So which option should I use to flash the zip file.
out386 said:
Chainfire had released a newer version of his SuperSU that doesn't need to modify the system partition to provide root access. This method doesn't have much of a practical application right now, but it allows you to flash OTA updates without having to unroot or flash the stock system partition.
HOW TO USE:
Download the attached zip, and flash it from a recovery (I tested it with TWRP).
Download SuperSU 2.56 (or newer, if it supports systemless mode) from here: http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 (Just download the apk)
Flash SuperSU-v2.56-20151030013730.zip
Reboot
This will work with all Marshmallow kernels, even the stock kernel.
Drawback : A factory data reset will remove superuser privileges. If that happens, simply flash SuperSU-v2.56-20151030013730.zip again.
TO RECEIVE OTA UPDATES :
Just make sure not to do anything that modifies /system. For example, no build.prop changes, and no system app removal. Or even if you do these, make sure to undo these changes before flashing an OTA. You can flash OTAs without unrooting now.
Flash the stock boot.img for your current Android version before flashing OTAs.
BUGS :
I didn't find any, yet, but Chainfire wrote the following on his thread:
Apps with hardcoded paths to su (seriously?) will bork
Factory reset unroots
Factory reset wipes pin
...
Bugs... Bugs everywhere!
ADDITIONAL INFO :
This zip will replace sepolicy as mentioned on Chainfire's thread (thanks to @metaspook for the patched sepolicy, which I extracted from his zip), so you'll be able to get root access even on SELinux enforcing kernels (only the stock MM kernels right now). Also, you can flash any other kernel (as long as it comes in a zip format, not as an img) before or after flashing this, and you'll still have root access.
Click to expand...
Click to collapse
Good work n thanks for mention bt can't understand why u created a patcher again where I'v already created one!
Its ok, good job.
Good.... Thanks for posting
metaspook said:
Good work n thanks for mention bt can't understand why u created a patcher again where I'v already created one!
Its ok, good job.
Click to expand...
Click to collapse
Yes, well, I would never have reposted the same thing, so, I'm sorry if it seemed like that.
This one uses Chainfire's new systemless root method. Unlike other root methods that need modifications to /system, this method uses modifications to the boot image to set up and run the su daemon from a loop device on the /data partition and achieve root. Right now, that doesn't have much of an advantage except to make flashing OTAs easier. Chainfire made it because future devices might need it. I made the patch because someone on FB asked about it.
<accidental double post, sorry. Can't delete>
kalpitandroid said:
I am using MicroMax Android One with Marshmallow
Currently, I've not tired the phone.
When I open recovery, I see some options like Apply update from SD card, mount, cache wipe, factory reset, etc.
So which option should I use to flash the zip file.
Click to expand...
Click to collapse
You need to install a custom recovery first. Go to the Android One (First generation) General forums on this site. You'll find a how-to at the very top of the list of threads. Once you have a custom recovery, flash this using the "install zip" option.
out386 said:
Yes, well, I would never have reposted the same thing, so, I'm sorry if it seemed like that.
This one uses Chainfire's new systemless root method. Unlike other root methods that need modifications to /system, this method uses modifications to the boot image to set up and run the su daemon from a loop device on the /data partition and achieve root. Right now, that doesn't have much of an advantage except to make flashing OTAs easier. Chainfire made it because future devices might need it. I made the patch because someone on FB asked about it.
Click to expand...
Click to collapse
Hmm... gotcha now.. Good work!
If u ever need any help just pm.
Thank you...
out386 said:
<accidental double post, sorry. Can't delete>
Click to expand...
Click to collapse
Special thanks to @funkyboy1281, @lentm, @macboy3000 for helping getting this work. As far as I can tell, this is the easiest and most straight forward instruction set for getting Android Pay to work on the latest version of Pure Nexus, Chroma, or OMNI Rom
Clean Flashing
Download the appropriate Rom.
Pure Nexus DiscussionChroma DiscussionOMNI (no link available, sorry)
Download Pure Nexus Dynamic Gapps 2-3-16 (Very important, you cannot use 15-3-16 or later). Yes, even if you use Chroma or OMNI, these Gapps should work for you. Link
Download the unSU script for completely unrooting before installing systemless root. Link
Download SuperSU 2.68 (or higher) Link || Discussion
Advance wipe in recovery all but internal storage
Install the ROM, gapps, and unSU
Optional: Install custom kernel
In TWRP, under advanced, go to terminal and type the following:
Code:
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu
Note: You may also do this using ADB in recovery (adb shell, and then enter the same commands. This is much easier in my opinion, and is the method I used.
Flash 2.68 beta in TWRP
Fully reboot, go through initial device setup
Verify in SuperSU that you cannot install SU to the system. This will verify that we are using the systemless root option
Download SafetyNet Helper and make sure it passes
Install Android Pay and profit!
Dirty Flashing
Verify that SafetyNet still passes in Android.
Verify in Android that /data/.supersu is still present and contains the appropriate options (see clean flashing). You may also verify in recovery by going to terminal commands and entering in:
Code:
cat /data/.supersu
Install the updated ROM (do not reinstall gapps unless your ROM builder specifically tells you to do so. Pure nexus does not require a reflash)
Optional: Install unSU. This was not necessary on PureNexus, but I cannot be sure for other roms. It shouldn't hurt anything to flash.
Optional: Install custom kernel
Install SuperSu 2.68 (or higher)
Check SafetyNet Helper and make sure it still passes
FAQ
Q. Can I still install and use AdAway?
A. Yes. You must first install something in recovery before installing AdAway. See the discussion Thread. You should be installing v3.1 of the app after you install the recovery zip.
Q. Can I still use V4A?
A. Yes. I do not use this however, but it has been reported that nothing special needs to be done.
Q. Can I change the screen density?
A. We have not found a way to do this without tripping Safety Net
..
@skaforey thanks for this thread! Might want to note in the OP that Wiping Data erases the internal storage. Some people may not know that.
MrBrady said:
@skaforey thanks for this thread! Might want to note in the OP that Wiping Data erases the internal storage. Some people may not know that.
Click to expand...
Click to collapse
Noted, thank you! Still hoping some of the lucky folks that have it working can help us out here.
Has anyone found a way to adjust the screen density while keeping Android Pay functional?
MrBrady said:
Has anyone found a way to adjust the screen density while keeping Android Pay functional?
Click to expand...
Click to collapse
You (should) be able to change the density through adb using
Code:
adb shell wm density DPI
with dpi being what you want, or if you have root you can do that from a terminal emulator, just remove the adb shell part.
I tried the 2nd method without formating data in different combos to no avail, still hesitant to wipe my internal sdcard, it shouldn't be that hard man, will follow this thread
anyone know other aosp ROMs that have AP working outside of pure nexus?
Sent from my Nexus 6 using Tapatalk
Following the steps in the top most instructions in the OP...
1) Pure Nexus 3/8 does not have root out of the box, so the Unroot step was not needed.
2) TWRP did not show any files/folders in the /su directory, so the Terminal command didn't work. I booted up the device and did it through the Terminal there instead and then rebooted.
After that, loaded up Android Pay and it says "Android Pay can't be used".
Running SafetyNet reports....
SafteyNet request: success
Response validation: success
CTS profile match: false
Tried different methods, not working for me.
1. Download Pure Nexus 1/03/16 or newer (Layers), the latest PN GApps, UnSU, the latest SuperSU.
2. Backup any important data.
3. Boot into TWRP and wipe everything including internal storage
4. Format data.
5. reboot TWRP with USB-OTG that has fines necessary.
6. Flash Pure Nexus.
7. Flash GApps.
8. Flash UnSU.
9. In terminal I saw I still had a folder /supersu so I deleted that.
reboot. Setup phone with google account. Did not have it restore apps, but did have it restore basic setup from google.
Install Safetynet helper
Still fail CTS Profile Match
Don't know what the people are doing different, but not working for me.
Are you using the PN-Gapps or others?
The updated-unsu is what date?
Thanks!
The only way I have gotten AP to work is from a stock image based ROM. It doesn't seem to work with AOSP ROMs like Pure Nexus.
For example, I am currently running Tupac's debloated stock ROM with Cataclysm MOD, Viper4Android and AdAway ad blocking. Android Pay works fine, as long as you follow the SU steps listed in the OP of this thread.
What I did to get AP to work was removing these lines from updater-script located in META-INF > com > google > android
Code:
ui_print("Flashing SuperSU..");
package_extract_dir("supersu", "/tmp/supersu");
run_program("/sbin/busybox", "unzip", "/tmp/supersu/supersu.zip", "META-INF/com/google/android/*", "-d", "/tmp/supersu");
run_program("/sbin/busybox", "sh", "/tmp/supersu/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/supersu/supersu.zip");
ui_print(" ");
and removed the supersu folder inside the zip file. I then installed my custom kernel and systemless supersu. After that, I set the permissions for bin folder inside su to 751 using a root explorer and deleted xbin_bind.
@macboy3000 what kernel and what version of SuperSU did you use, ? I tried your method, ROM booted fine but safetynet test failed...
this is how I did it
unzip ROM
edit code out
delete supersu folder
zip ROM
advance wipe everything but internal
flash ROM
flash pn gapps
flash elemental kernel
flash supersu
boot into android, delete xbin_bind
reboot system
permissions on bin folder were already 751, so didn't need to change
Sent from my Nexus 6 using Tapatalk
sgloki77 said:
@macboy3000 what kernel and what version of SuperSU did you use, ? I tried your method, ROM booted fine but safetynet test failed...
this is how I did it
unzip ROM
edit code out
delete supersu folder
zip ROM
advance wipe everything but internal
flash ROM
flash pn gapps
flash elemental kernel
flash supersu
boot into android, delete xbin_bind
reboot system
permissions on bin folder were already 751, so didn't need to change
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Weird...I'm using SuperSU 2.67 and I'm also using Elemental kernel.
macboy3000 said:
Weird...I'm using SuperSU 2.67 and I'm also using Elemental kernel.
Click to expand...
Click to collapse
Did you format data? I'll give it a shot with 2.67, I used 2.68
Sent from my Nexus 6 using Tapatalk
sgloki77 said:
Did you format data? I'll give it a shot with 2.67, I used 2.68
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I formatted everything except internal storage before installing.
macboy3000 said:
What I did to get AP to work was removing these lines from updater-script located in META-INF > com > google > android
Code:
ui_print("Flashing SuperSU..");
package_extract_dir("supersu", "/tmp/supersu");
run_program("/sbin/busybox", "unzip", "/tmp/supersu/supersu.zip", "META-INF/com/google/android/*", "-d", "/tmp/supersu");
run_program("/sbin/busybox", "sh", "/tmp/supersu/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/supersu/supersu.zip");
ui_print(" ");
and removed the supersu folder inside the zip file. I then installed my custom kernel and systemless supersu. After that, I set the permissions for bin folder inside su to 751 using a root explorer and deleted xbin_bind.
Click to expand...
Click to collapse
Well I tried this and still no luck
I even tried flashing the modified ROM, gapps, and never flashing SuperSU at all (so my rom wasn't rooted at all), and SafetyNet still gives me a red screen. I really wish I knew what was triggering this for some and how others can make it work.
I tried again using 2.57 SuperSU and Elemental X and still fails. Would someone that got it working be able to post a more detailed log of exactly what steps you're using and exactly what files you're flashing.
MrBrady said:
The only way I have gotten AP to work is from a stock image based ROM. It doesn't seem to work with AOSP ROMs like Pure Nexus.
For example, I am currently running Tupac's debloated stock ROM with Cataclysm MOD, Viper4Android and AdAway ad blocking. Android Pay works fine, as long as you follow the SU steps listed in the OP of this thread.
Click to expand...
Click to collapse
This has been my experience as well !
jcrompton said:
This has been my experience as well !
Click to expand...
Click to collapse
Got Android Pay working with Tupac's debloated stock ROM too! Thanks!
Is it possible to change DPI and keep Android Pay working?
lentm said:
Got Android Pay working with Tupac's debloated stock ROM too! Thanks!
Is it possible to change DPI and keep Android Pay working?
Click to expand...
Click to collapse
Not that I have found, unfortunately. Even via just ADB commands.