Related
HI all,
Ca you help me in flashing RCmixHD [2.3.3,SENSE 2.1,720p video,tb unlock] v1.0.1 ROM. I need to know which are the files I have to download and flash. Thanks in Advance.
With regards
<Manic>
There is a whole section titled ROM links, it shouldn't be that hard to work out :/
If you're generally referring to flashing a custom rom then have a good read at the Nexus One wiki, it'll help you understand a little more.
manicsen said:
HI all,
Ca you help me in flashing RCmixHD [2.3.3,SENSE 2.1,720p video,tb unlock] v1.0.1 ROM. I need to know which are the files I have to download and flash. Thanks in Advance.
With regards
<Manic>
Click to expand...
Click to collapse
ill upload it. the rom seems to be only showing up as 1.01mb on the OP thread. ill post link when im done
charlieb620 said:
ill upload it. the rom seems to be only showing up as 1.01mb on the OP thread. ill post link when im done
Click to expand...
Click to collapse
It might help if you read the posting fully. You need to download all three files.
1. RCmixHD 1.0
2. USB Fix
3. 1.0.1 Update
Install them in this order, reboot between each install. And make sure you fully wipe your device first.
What about for Version 1.1.. I think i can download that single file and flash the ROM..
hi,
i downloaded RCmixHD [2.3.3,SENSE 2.1,720p video,tb unlock] v1.1 ROM and flashed it after full wipe..
During the time of flashing i am getting this message.. Kindly help me in clearing this problem
E:Missing file:
ext/system-VR/0419/libCBLexMgr.0419.so
E: Verification failed
zip verification failed
zip isn't signed correctly.
Installation aborted..
manicsen said:
hi,
i downloaded RCmixHD [2.3.3,SENSE 2.1,720p video,tb unlock] v1.1 ROM and flashed it after full wipe..
During the time of flashing i am getting this message.. Kindly help me in clearing this problem
E:Missing file:
ext/system-VR/0419/libCBLexMgr.0419.so
E: Verification failed
zip verification failed
zip isn't signed correctly.
Installation aborted..
Click to expand...
Click to collapse
Disable signature verification(If you're using RA Recovery, you can see 'toggle signature...', and I think Clockwork also has such option) and try it again.
Hi,
Is it Safe to flash Unsigned ROM.. or i have to wait for Signature once full ROM is there..
<Manic>
manicsen said:
Hi,
Is it Safe to flash Unsigned ROM.. or i have to wait for Signature once full ROM is there..
<Manic>
Click to expand...
Click to collapse
Although it warns about unsigned ROM/updater, I think if it is from reliable developer, it's usually OK, though I feel developers should sign their .zip files after packing is done.
thanks.. i have flashed already
hi i m trying to update my gt540 from cyanogenmod (swiftdroid v2.0 M4) to cyanogenmod (swiftdroid v2.0 M5).this shows error assert failed: write_raw_image("temp/boot.img","boot") .please help .i m wondering what to do???
This is a known bug with M5. The update has installed, but the boot.img hasn't been flashed. Here is what you need to do.
Extract boot.img from the update .zip file. If you can boot into swiftdroid, use YaffsExpert to flash the boot.img.
Hope it helps,
Jack
JackG256 said:
This is a known bug with M5. The update has installed, but the boot.img hasn't been flashed. Here is what you need to do.
Extract boot.img from the update .zip file. If you can boot into swiftdroid, use YaffsExpert to flash the boot.img.
Hope it helps,
Jack
Click to expand...
Click to collapse
is there a version that already has the fix applied? i tried the one on the main thread that was supposed to be fixed, but it still gave this error msg.
Same problem for me.
I don't think the installation completes since the installation seems to abort before system.img is flashed.
I could always try fastboot but I'd wait for a fix.
No it works fine, it aborted at the boot.img. so just reboot and uses the terminal to complete the update.
are you 100% sure? have you tried it? i don't think the phone will boot if the boot.img is corrupt.
nibras_reeza said:
are you 100% sure? have you tried it? i don't think the phone will boot if the boot.img is corrupt.
Click to expand...
Click to collapse
If you were to look at the updater-script file in the update.zip file, the system partition is modified first. Also, the boot.img isn't corrupt, the update script has an error in it which aborts the boot.img flash. But if you flash the boot.img via fastboot or YaffsExpert, it works perfectly.
Jack
For reference's sake, the issue has been fixed I guess.
SwiftDroid v2.0 M5 Fixed
Recovery:http://swift.kulkoff.com/SwiftDroid_v2.0_recovery_M5.zip
Fastboot:http://swift.kulkoff.com/SwiftDroid_v2.0_fastboot_M5.zip
Hey guys,
so, a lot of my quetstions will be already posted, but i can´t find them all.
So i hope i annoy no one here ;-).
Ok, now to the important:
I have a SGS until 6 month. over the time i learnd a lot of android and i´m very lucky with them.
Then i heard from cyanogenmod. and all i read about it is great.
i have knowledges about root of linux an so of android.
So, during my research i have a lot of question before i flash my sgs:
- i found only one forum enty where i read i have to format all partitions.
So, how do i flash a sgs?
i have a modded boot rom with root and clockwork mod.
I tried a backup of the system.
the rom manager don´t show ne the cm7 mod for my device.
Do anyone know why? because the RC status?
When i get an error, how can i rollback my firmware with the backup?
Which pc software i need?
my plan ist to flash the sgs with the experimental version, no nightly build.
CWM makes al lot if IMG files. the cm7 zip has only one IMG.
So, i hope anyone can tell some or send my some nice links.
thanks a lot :-D
ravn
Use this
Boom, that's how it's done folks.
Sent from my I9000m running Cyanogen Mod Nightly
Hey,
thanks guys.
So, can anyone explain me how i can go back to the original rom if i got any probs or even i want?
So, i made a backup with Titanium Backup (premium user) and secondly with CWM.
So, i copied them to my PC.
CWM makes some IMG files. So, how can i rollback them to my device?
Also if i try to create a rom image with the rom manager the recovery manager makes a error.
:-D
So, i get by saving my rom the following error:
-- Installing package ...
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Why do the rom manager want to install a package by making an backup?
PS: i have the rooted bootloader: PDA_XXJVK_Sbl.tar installed.
to revert back to you need to revert to a stock rom. using odin and a full PDA froyo will do the job.
Hey,
so u mean, i have to download the offical rom and install them over odin.
then i have to root them and install CWM and reverse the backup.
is that right?
ravn83 said:
Hey,
so u mean, i have to download the offical rom and install them over odin.
then i have to root them and install CWM and reverse the backup.
is that right?
Click to expand...
Click to collapse
yes.. that will be the proper way to do it.
I have a non-rooted phone with TWRP installed. When the phone tries to install the MDL update, the phone boots into recovery, but goes to TWRP. And it fails each time. Has anyone else successfully loaded the update with TWRP installed on a non-rooted phone? Do I need to remove TWRP to get this to work and, if so, how is that done?
Here's the log from TWRP:
Running boot script...
Finished running boot script.
I:Inserting 'install =/cache/321a2cb29b9c.update_SPH-L720_MDC_CSB_user_RP_to_MDL_CSB_user_RP-1.zip'
I:Copying file /cache/recovery/log to /cache/recovery/last_log
I:Attempt to load settings from settings file...
I:Loading settings from '/data/media/0/TWRP/.twrps'.
I:Backup folder set to '/external_sd/TWRP/BACKUPS/cdc9d69d'
I:Version number saved to '/cache/recovery/.version'
I:Switching packages (TWRP)
I:Set page: 'action_page'
Processing AOSP recovery commands...
I:command is: 'install' and I:value is: '=/cache/321a2cb29b9c.update_SPH-L720_MDC_CSB_user_RP_to_MDL_CSB_user_RP-1.zip'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Full zip path: '/external_sd/=/cache/321a2cb29b9c.update_SPH-L720_MDC_CSB_user_RP_to_MDL_CSB_user_RP-1.zip'
Installing zip file '/cache//321a2cb29b9c.update_SPH-L720_MDC_CSB_user_RP_to_MDL_CSB_user_RP-1.zip'
Installing '/cache//321a2cb29b9c.update_SPH-L720_MDC_CSB_user_RP_to_MDL_CSB_user_RP-1.zip'...
Checking for MD5 file...
I:Cannot find file /cache//321a2cb29b9c.update_SPH-L720_MDC_CSB_user_RP_to_MDL_CSB_user_RP-1.zip.md5
Skipping MD5 check: no MD5 file found.
Register_libbootloader_updater Qcom msm8960
Verifying current system...
partition read matched size 9214720 sha 752ba02ce73412313a123b43ac0ae9bc46e13d22
partition read matched size 52009728 sha 52d27452b5e779ba0fdb676c453d3f2d1f294569
2049134592 bytes free on /cache (87488677 needed)
script aborted: assert failed: getprop("ro.secure")=="1"
assert failed: getprop("ro.secure")=="1"
E:Error executing updater binary in zip '/cache//321a2cb29b9c.update_SPH-L720_MDC_CSB_user_RP_to_MDL_CSB_user_RP-1.zip'
E:Error installing zip file '/cache//321a2cb29b9c.update_SPH-L720_MDC_CSB_user_RP_to_MDL_CSB_user_RP-1.zip'
Done processing script file
I installed OUDHS ( http://forum.xda-developers.com/showthread.php?t=2254678 ) over TWRP and still get the same error I bolded from the log above.
Can someone please tell me how to get the stock recovery back? Do I need to flash/odin the base ROM? If so, where can I find the Sprint version?
You want to unroot? There are threads on the MDL update with flashable versions. Read thoroughly because a lot has changed.
Here: http://forum.xda-developers.com/showthread.php?t=2270065
jejb said:
I installed OUDHS ( http://forum.xda-developers.com/showthread.php?t=2254678 ) over TWRP and still get the same error I bolded from the log above.
Can someone please tell me how to get the stock recovery back? Do I need to flash/odin the base ROM? If so, where can I find the Sprint version?
Click to expand...
Click to collapse
Here - I placed the Stock Recovery in tar form on RWilco12's Repo. Just flash With Odin.
I'll be making a one click for this as well. (I'll also make sure all the stock items are tar'd and in one click formats.)
http://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung%20Galaxy%20S4%20%28SPH-L720%29/Recovery/Stock/MDC
As far as the update failing or not, and if you want to go back completely stock; there are also MDC NoData and Full Restore tars and in his Repo. Depending on your flash history, you may want to obtain root and use Chainfrire's Triangle Away. (Even though the i9505 variant isn't on his supported list, it does work resetting the binary counter) Then you'd want to flash the stock build.
http://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung%20Galaxy%20S4%20%28SPH-L720%29/Stock%20ROMs/MDC/
MoHoGalore said:
Here - I placed the Stock Recovery in tar form on RWilco12's Repo. Just flash With Odin.
I'll be making a one click for this as well. (I'll also make sure all the stock items are tar'd and in one click formats.)
http://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung%20Galaxy%20S4%20%28SPH-L720%29/Recovery/Stock/MDC
Click to expand...
Click to collapse
Thanks much! But I'm having an issue loading this. The Odin load started off well, but it's been sitting in the following state for like 10 minutes now. I'm afraid to unplug the phone/stop the update for fear of having a brick. Loading TWRP and OUDHS with Odin only took a few seconds, so it's not looking good.
jejb said:
Thanks much! But I'm having an issue loading this. The Odin load started off well, but it's been sitting in the following state for like 10 minutes now. I'm afraid to unplug the phone/stop the update for fear of having a brick. Loading TWRP and OUDHS with Odin only took a few seconds, so it's not looking good.
Click to expand...
Click to collapse
Looks like you renamed the file. Did you?
Pull battery, boot back into Odin mode and don't rename the file. There's no reason to. It should be .tar.md5
No. I did notice the rename when my Win7 system pulled it down, but I did nothing to it explicitly.
jejb said:
No. I did notice the rename when my Win7 system pulled it down, but I did nothing to it explicitly.
Click to expand...
Click to collapse
Look at my post above. I added a picture. There shouldn't be anything renaming it.
Download a fresh copy, pull battery, get back to Odin mode and re-flash.
MoHoGalore said:
As far as the update failing or not, and if you want to go back completely stock; there are also MDC NoData and Full Restore tars and in his Repo. Depending on your flash history, you may want to obtain root and use Chainfrire's Triangle Away. (Even though the i9505 variant isn't on his supported list, it does work resetting the binary counter) Then you'd want to flash the stock build.
http://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung%20Galaxy%20S4%20%28SPH-L720%29/Stock%20ROMs/MDC/
Click to expand...
Click to collapse
So in reading about Triangle Away, it seems I may have screwed myself up by loading a custom recovery, even though I'm not rooted? That sucks, if so. But I've not read about anyone else having issues like this and I can't be the only one to have loaded a custom recovery and tried to do the update. Thanks for the procedure, though. I guess I may have to try all of that to get back to stock (if the phone isn't bricked, still trying to load).
Delete
jejb said:
So in reading about Triangle Away, it seems I may have screwed myself up by loading a custom recovery, even though I'm not rooted? That sucks, if so. But I've not read about anyone else having issues like this and I can't be the only one to have loaded a custom recovery and tried to do the update. Thanks for the procedure, though. I guess I may have to try all of that to get back to stock (if the phone isn't bricked, still trying to load).
Click to expand...
Click to collapse
It's not bricked. It's just a failed flash. You have a few choices.
My recommendation for you;
1. Get the rooted, nodata, MDC One Click, the exe. (That way we know nothing will be renaming the file)
2. Put your phone in Odin mode and flash.
3. Go get Chainfire's Triangle Away v2.90 (This is a link to Chainfire's XDA thread which is permissible)
4. Use the app.
5. Backup anything you'd like to keep to pc.
6. Go get the Stock MDC Full Restore and flash via Odin.
Now you'll be back to stock, un-rooted and Official on build and binary and can apply the update from OTA.
You can get the stock build from the Repo.
Turns out it was IE that was forcing the rename on the file. So I pulled it down with firefox and it did not rename it. But when I try to load it, it tells me the MD5 hash did not match and ends. So I took the MD5 off the end and tried it just as a .tar file. Got the same endless load as the first time I tried it above.
I may have to go through the steps you spelled out in your last post, and I really appreciate you taking the time to do that. But shouldn't this stock recovery at least load? I'm a bit worried that if this file won't load, will the others I pull down from the same download site give me the same issues?
Give me a min and I'll upload my tested copy to dev host so you'll have an md5 to compare. Possible it was a bad upload from me to the repo.
Sent from my SPH-L720 using Xparent Skyblue Tapatalk 2
:Edit: Here's the tested copy of the Recovery. http://d-h.st/0fp
MoHoGalore said:
Give me a min and I'll upload my tested copy to dev host so you'll have an md5 to compare. Possible it was a bad upload from me to the repo.
Sent from my SPH-L720 using Xparent Skyblue Tapatalk 2
:Edit: Here's the tested copy of the Recovery. http://d-h.st/0fp
Click to expand...
Click to collapse
Thank you SO much! That copy did work successfully via Odin to put the stock recovery back on the phone. And the MDL update ran successfully after that was done. So I'm now up to the latest level and not rooted. I'll probably put the OUDHS recovery on again now that I have a good copy of the stock recovery that I can always go back to if needed.
It's folks like you that make this board such a valuable resource. Thanks again.
Good to know you got up and running. And I replaced it again on the Repo. Looks like Dev Host went down in the last few minutes so I was worried if you got it or not.
Glad to help. :beer:
This is a build at a really early stage so take care !
Ok, so the method I propose is absolutely non intrusive. You might want to flash the recovery you'll find here-under but I personally haven't done it so feel free to go first Flashing back the original recovery shouldn't be a big deal anyway.
Prerequisite
You should have installed:
K910 ADB Driver (available on the CD that appear when you connect the device)
ADB
Fastboot
Rooting
So the method is pretty easy:
Download the latest SuperSU update.zip and put it at the root of your Internal SD Card
(Optional) Download Google Apps for Android 4.2.2 (thanks to TeamAndroid) and put it at the root of your Internal SD Card
Download the recovery.img (build 140205)
un-7zip it
Restart your device in the bootloader:
Code:
adb reboot-bootloader
Boot your phone into the ClockworkMod recovery:
Code:
fastboot boot cwm_recovery_custom.img
Install zip, wipe partition, backup/restore, adb sideload, ...
Reboot
The phone is left untouched except for the zip you flashed.
Update on the 6th of February (Build 140205):
Bigger font
/sdcard mounted on the first user's internal storage (= symlink /sdcard /data/media/0)
Makes use of the latest kernel
The old recovery.img stays available.
For those who would be stuck on K910_SS_S_2_040_0039_131101, I posted the official update.zip here
How to build my own recovery
If you are curious about building the recovery, I'll post here a few tips.
First of all, you'll need a good tutorial like the one on XDA University. The steps are the following:
Prepare your OS to receive a cyanogenmod repository. I would advice an Ubuntu so you can following this guide. Note that this is for a plain Android so you need to stop following it when they issue the first repo command
Then you need to carefully read this guide on porting CyanogenMod ROM. You don't need to build the full system (which is a completely other story) but only the recovery. I prepared the vendor directory for you (base on LG Optimus and a lot of research).
The building happens according to this guide.
You could be done by now if it wasn't for the dtb. If you try to boot your recovery as is, fastboot will complain about it. You'll find other people having the same issue, just follow their solution.
csu333 said:
This is a build at a really early stage so take care !
Ok, so the method I propose is absolutely non intrusive. You might want to flash the recovery you'll find here-under but I personally haven't done it so feel free to go first Flashing back the original recovery shouldn't be a big deal anyway.
So the method is pretty easy:
Download the recovery.img
un-7zip it
Restart your device in the bootloader:
Code:
adb reboot-bootloader
Boot your phone into the ClockworkMod recovery:
Code:
fastboot boot recovery-clockwork-6.0.4.6-kiton.img
Install zip, wipe partition, backup/restore, adb sideload, ...
Reboot
The phone is left untouched except for the zip you flashed.
More precisions to come in a next edit.
Click to expand...
Click to collapse
Yess!!! Thanks!!!
creating boot image...
creating boot image - 4493312 bytes
downloading 'boot.img'...
OKAY [ 0.142s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.155s
What rom version did you have when boot .img?
cwm (loki) .img from lg g2 says ok afterall, but phone restarts after showing me a nice blue line .
take a look https://gitlab.com/itsmikeramsay/mkbootimg/tree/master and this http://looollll.doorblog.jp/archives/29337755.html and this http://forum.xda-developers.com/showthread.php?t=2469510
I believe this really may be helpful to you http://forum.xda-developers.com/showthread.php?t=2073775
katalinscrob said:
creating boot image...
creating boot image - 4493312 bytes
downloading 'boot.img'...
OKAY [ 0.142s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.155s
QUOTE]
Same result for me too.
Click to expand...
Click to collapse
katalinscrob said:
creating boot image...
creating boot image - 4493312 bytes
downloading 'boot.img'...
OKAY [ 0.142s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.155s
What rom version did you have when boot .img?
cwm (loki) .img from lg g2 says ok afterall, but phone restarts after showing me a nice blue line .
take a look https://gitlab.com/itsmikeramsay/mkbootimg/tree/master and this http://looollll.doorblog.jp/archives/29337755.html and this http://forum.xda-developers.com/showthread.php?t=2469510
I believe this really may be helpful to you http://forum.xda-developers.com/showthread.php?t=2073775
Click to expand...
Click to collapse
I have K910_SS_S_2_040_0109_131226 but it shouldn't be an issue anyway. This sounds like I uploaded the wrong recovery (I have so many) because "dtb not found" is the message you receive when, well, the DTB doesn't appear in the recovery. Adding the DTB is the very last step to build the recovery.
Try this one instead.
Just for your information, note that following the guide I mentioned earlier did work but I have to add a custom init.rc because there was no backlight on the screen.
csu333 said:
I have K910_SS_S_2_040_0109_131226 but it shouldn't be an issue anyway. This sounds like I uploaded the wrong recovery (I have so many) because "dtb not found" is the message you receive when, well, the DTB doesn't appear in the recovery. Adding the DTB is the very last step to build the recovery.
Try this one instead.
Just for your information, note that following the guide I mentioned earlier did work but I have to add a custom init.rc because there was no backlight on the screen.
Click to expand...
Click to collapse
Other possible root???
http://lenovobbs.cnmo.com/thread-14620407-1-1.html
sakilxda said:
Other possible root???
http://lenovobbs.cnmo.com/thread-14620407-1-1.html
Click to expand...
Click to collapse
I honestly doubt it: all the 1 click root I've seen until know are based on a bug in the backup mechanism that have been fixed for a while now. But since it seems pretty recent, anything is possible. I can't confirm since I'm rooted now
Right now with this method, and when I get my Lenovo steps that I can do?
Update first and then use this method to root?
I do not understand English, use google translate, and as I see there seems to be no problems?
Still it take at least 2 weeks to receive it and I'm sure there will be changes and improvements ...
Thanks again for sharing your experiences.
Big thanks button should be available too...
Managed to boot in cwm, root from cwm (btw very nice option ), Gapps full reinstall and finally a backup. EVRIKA! YOU DID IT ! Respect man ! permanent img flash would be next step I assume...
sakilxda said:
Right now with this method, and when I get my Lenovo steps that I can do?
Update first and then use this method to root?
I do not understand English, use google translate, and as I see there seems to be no problems?
Still it take at least 2 weeks to receive it and I'm sure there will be changes and improvements ...
Thanks again for sharing your experiences.
Click to expand...
Click to collapse
You're right: best method is to upgrade then root with this method. If it seems difficult to get the upgrades, I can post the zip files (it took me more than a week to get the first one).
katalinscrob said:
Big thanks button should be available too...
Managed to boot in cwm, root from cwm (btw very nice option ), Gapps full reinstall and finally a backup. EVRIKA! YOU DID IT ! Respect man ! permanent img flash would be next step I assume...
Click to expand...
Click to collapse
You're very welcome
Well, actually, there should be no problem flashing this recovery, it's just that it could break the OTA process (and that I haven't tested it myself yet)
So next step after testing is to find a way to make this menu readable. I mean, I almost need a magnifying glass to read it :laugh:
It isn't really an issue, maybe to correct the dafult push backup folder to internal sdcard clockworkmod instead of root folder (mnt...). I suppose that until seriously modded ROM's will appear it's best to mantain non flashed anyway for the OTA capability IMHO. Anyway, very nice job, put a paypal to receive some beers from us.
I still cannot install zips (SuperSU / gapps) from recovery, though recovery.img was flashed without any error. Am I missing anything?
Hello friends, you have seen this guide?
http://lenovo-forums.ru/topic/4131-...-lenovo-vibe-z-k910-пока-только-wcdma-версия/
sakilxda said:
Hello friends, you have seen this guide?
http://lenovo-forums.ru/topic/4131-...-lenovo-vibe-z-k910-пока-только-wcdma-версия/
Click to expand...
Click to collapse
It is based on csu333's work. I linked thid thread to russian fellows.
katalinscrob said:
It is based on csu333's work. I linked thid thread to russian fellows.
Click to expand...
Click to collapse
Ok, just thought it was a copy
nlohani said:
I still cannot install zips (SuperSU / gapps) from recovery, though recovery.img was flashed without any error. Am I missing anything?
Click to expand...
Click to collapse
Are you sure you are in the custom recovery? The Lenovo one look similar but doesn't have the clockwork mod logo in the background. It lets you install zip...as long as they are signed by Lenovo.
csu333 said:
Are you sure you are in the custom recovery? The Lenovo one look similar but doesn't have the clockwork mod logo in the background. It lets you install zip...as long as they are signed by Lenovo.
Click to expand...
Click to collapse
You are right, after re-flashing your recovery I was able to install SuperSU.zip, but still couldn't find it in the device.
Just to share further-
1. Titanium backup still fails to get root access
2. One root checker application says my device is rooted, but 'rescue root checker' says it is not
katalinscrob said:
It isn't really an issue, maybe to correct the dafult push backup folder to internal sdcard clockworkmod instead of root folder (mnt...). I suppose that until seriously modded ROM's will appear it's best to mantain non flashed anyway for the OTA capability IMHO. Anyway, very nice job, put a paypal to receive some beers from us.
Click to expand...
Click to collapse
Good suggestions. I'll take a look.
Now that I know what it takes to build a recovery, I'll think twice before starting a project of a really modded ROM
nlohani said:
You are right, after re-flashing your recovery I was able to install SuperSU.zip, but still couldn't find it in the device.
Just to share further-
1. Titanium backup still fails to get root access
2. One root checker application says my device is rooted, but 'rescue root checker' says it is not
Click to expand...
Click to collapse
I 've had the same behavior with the oldest ROM. This is why I provided a custom ROM with busybox installed even if I knew most people wouldn't need it. It was just impossible to install it afterwards. It might then be version related. Which version are you running?