Develop Bugs

[RECOVERY] CWMR 5.5.0.4 for I957 (LTE)

Hello,
I have ported the latest clockworkmod recovery to the galaxy 8.9 LTE i957 tablet.
This is a recovery and not a kernel, thus you can run whatever you wish.
Instructions:
0) MAKE SURE YOU HAVE AN I957, do not flash this otherwise.
1) Flash this file via ODIN: CWMR5x_i957_recovery.tar.md5
2) Attempt a backup (there appears to be a bug in 5.5.0.4 that long names can possibly cause it to hang during a backup.) If it works or fails, reboot and mount your tablet in your OS. If you get hung, adb shell into your device and reboot it.
3) After your tab is mounted, go into the clockworkmod folder and create an EMPTY FILE with NO EXTENSION called .hidenandroidprogress
Note the period and lack of extension. This prevents the backup routine from enumerating the file list which I suspect is causing the hang during backup.
This is considered an ALPHA release with only two users thus far. No loss of data or damage was caused in the testing of this file. Please try it and report any issues you have with it. I am hoping this opens up the development for this device. I personally dont have it nor did I have access to one when I ported this so I need the community's help to track down issues/bugs. This was a pretty big challenge to get everything working right.
The full device tree I built for this can be found here:
android_device_samsung_SGHI957
Feel free to use this however you wish, though please give credit if it helps you devs.
Thanks to orlandoxpolice and jaywheelz for patiently testing this thus far.

OP updated with alpha build

Thanks for all your hard work
Sent from my SAMSUNG-SGH-I727 using xda premium

Thanks utkanos all the work is much appreciated.

This is amazing utkanos!
I'm gonna send ya another donation for all your hard work!
wahoooo!
Oh and hey I helped too, sacrificed one tab to the samsung gods!

I have tested everything with this recovery except for sd card re partitioning, wipe data / factory reset, and restore (nandroid).
Known Issues:
If you enter key test, you cant back out.
nandroid backup may hang for some users, the .hidenandroidprogress may have fixed this.
mounting and unmounting data is finicky sometimes.

Orlando is this the same file we had last night? Or it's it slightly changed since then?

Same file. I also installed cwm from market and enabled quick recovery and it worked
Sent from my SAMSUNG-SGH-I957 using xda premium

I thought cwm from the market causes our tab to go haywire. Is it the as what utkanos did or a different version?

You can install the program just don't flash its recovery. Go into options and enable quick recovery
Sent from my SAMSUNG-SGH-I957 using xda premium

Yeah I've been using quick boot from the market.

Any updates?
I'm finally done moving so should be available again.

Development is done until we get more testers
Sent from my SAMSUNG-SGH-I727 using xda premium

Recovery
Ok guys
I installed the recovery in my new SGH-I957 and all went well, now I have only tried the "wipe Dalvik cache" and it works great!
Utkanos Thanks for the work done!
Max

Ikaro said:
Ok guys
I installed the recovery in my new SGH-I957 and all went well, now I have only tried the "wipe Dalvik cache" and it works great!
Utkanos Thanks for the work done!
Max
Click to expand...
Click to collapse
Try to make a backup

orlandoxpolice said:
Try to make a backup
Click to expand...
Click to collapse
First testing the backup, the tablet hangs while copying the file "android.hardware.location.xml"
So I created the file ".hidenandroidprogress" (with Polaris office) and I have saved in the dir "clockworkMod/backup." I tried again to backup and it worked.
Now I have to try a restore, but I will tomorrow or the next!
Max

Awesome!
Look forward to hearing the results of the restore!

So was a restore successful?
If so, I may factory reset mine, root, wipe all the junkware/bloatware, garbage bookmarks, do my browser tweaks, a few other random bits and pieces, and post it up here as a cleaned up, rooted stock rom.

Don't have the success of installing it.. it said is a wrong tar or md5 file and it soft bricked it.. guess I'll wait for the next update.. thanks again
Sent from my SAMSUNG-SGH-I957 using XDA App

Will give this a Sticky and thanks for doing it

[ROM] Stock rooted 6.3

In keeping with my tradition of providing stock rooted ROMs, I've re-packaged the new 6.3 update. As with my past ones, this is completely stock except for modifications that provide root access. It does not attempt to block OTAs in any way, and it does not contain any extras like the Market.
This is a full ROM, not an incremental update, so it will wipe your /system partition when installing. If you're coming from a non-stock ROM you'll want to wipe data/cache, but if you're coming from a previous stock ROM you should be okay. This is tested in CWM (it's what I have onhand right now) but TWRP should also work.
Changes between this and a completely stock 6.3 ROM are:
REMOVED FROM ROM
The new /system/bin/check_rooted binary
Stock recovery image
Stock bootloader image
That goofy userdata-backup.zip
ADDED TO THE ROM
Superuser
su
busybox
CHANGES
Removed the entry from init.omap4430.rc that ran check_rooted at boot.
Set ro.secure=0 so adbd runs as root (insecure boot version only)
updater-script doesn't attempt to install recovery, bootloader, or userdata-backup.zip file since they are not in the ROM.
updater-script won't check your /system partition's size before installing. This means it will install on a /system partition that's been resized, but I have not tested this. My assumption is that if you resized /system you'll know how to handle any errors that you may encounter.
I'm providing secure and insecure boot images, as with my past versions. For those unfamiliar, insecure means adbd runs as root on your Fire so you get a root shell when you use adb to connect (i.e. you get # by default). Secure gives you a user shell (the $) by default, but you can still use 'su' to elevate to root.
DOWNLOADS
Stock rooted 6.3, secure boot image (md5: 37f51cd2dfaf58baffac09135236de36)
Stock rooted 6.3, insecure boot image (md5: e551a507ebc64fabe09f7d5387348585)​

What's change on 6.3??
Sent from my LG-P500 using xda premium

acax456 said:
What's change on 6.3??
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Its right there in his description..
Sent from my Nexus One using xda premium

acax456 said:
What's change on 6.3??
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
http://www.amazon.com/gp/help/customer/display.html/ref=hp_k6land_software2?nodeId=200790620

So if I flash this off Modaco gr7 to get to the latest version should I be ok as long as I wipe Dalvik and cache?

CTTKDKing said:
So if I flash this off Modaco gr7 to get to the latest version should I be ok as long as I wipe Dalvik and cache?
Click to expand...
Click to collapse
I would say probably yes since it's mostly stock, but I've never tried so I can't say for certain. Worst case should be that you bootloop, at which point you can always go back into recovery and wipe data, too.

Perhaps the dumb question, shall I just download and flash it by TWRP like other CM Roms? Please excuse I am noob. Thank you

eldarerathis said:
I would say probably yes since it's mostly stock, but I've never tried so I can't say for certain. Worst case should be that you bootloop, at which point you can always go back into recovery and wipe data, too.
Click to expand...
Click to collapse
Just flashed over Modaco GR7 throught TWRP and everything went smoothly and fine!
---------- Post added at 08:20 PM ---------- Previous post was at 08:19 PM ----------
ka724ka said:
Perhaps the dumb question, shall I just download and flash it by TWRP like other CM Roms? Please excuse I am noob. Thank you
Click to expand...
Click to collapse
Just Flashed through TWRP like any other rom (over modacos) and everything went fine !

My first kindle rom. Thanks so much. I really like stock and was happy to make this my first rom. It's awesome.

Just wondering if I can flash intersects kernel with the 6.3 Rom?
Sent from my Kindle Fire using xda premium

xolanir said:
Just wondering if I can flash intersects kernel with the 6.3 Rom?
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I don't see why not
Sent from my Kindle Fire using xda premium

Updated successfully, but for some reason CWM is unable to make a back up, gives me an error listing that it can't write the cache img. Has anyone else had this issue or is it isolated, and is there a fix? Thx in advance for help.
Sent from my Kindle Fire using xda premium

I assume this has the new browser, how do you access the new "reading view" I feel like it should be fairly easy to see but...

xolanir said:
Updated successfully, but for some reason CWM is unable to make a back up, gives me an error listing that it can't write the cache img. Has anyone else had this issue or is it isolated, and is there a fix? Thx in advance for help.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I've had CWM (and TWRP, actually) refuse to mount my cache partition in the past, and rebooting generally fixed it for me. Not sure if that's what's happening to you, though.

eldarerathis said:
I've had CWM (and TWRP, actually) refuse to mount my cache partition in the past, and rebooting generally fixed it for me. Not sure if that's what's happening to you, though.
Click to expand...
Click to collapse
I recently repartitioned my KF following the guide you posted using the GNU parted method. What I did was increased my media storage and shrunk my cache partition to 350MB and userdata partition to 700MB, would those settings affect CWM in anyway? The other thing I noticed was after I get the error, I reboot and check the CWM folder to see if anything did save, and it looks like it doesn't compress the back up while saving it. I found a partial back up of 2.35GB after the error. This is a strange one
Update: okay figured it out. The problem was CWM was trying to back up the /sd-ext volume. I unchecked it in the advanced back up option and ran the back up without a hitch.
Sent from my Kindle Fire using xda premium

Can anyone confirm that the browser did not update to the newest version?
To access reading view, I was told "At the bottom of the display there is an eyeglass Icon tap it the screen says loading and you will have the view. Back arrow out of it."
I don't see an eyeglass icon on this rom.

jacewt said:
Can anyone confirm that the browser did not update to the newest version?
To access reading view, I was told "At the bottom of the display there is an eyeglass Icon tap it the screen says loading and you will have the view. Back arrow out of it."
I don't see an eyeglass icon on this rom.
Click to expand...
Click to collapse
It works for me, but only on certain web pages (I'm guessing ones that are text-heavy). Try viewing some random Wikipedia article, for example. The icon also doesn't appear until about a second or so after the page has completely finished loading.

Just bizarre, I am not getting it. I looked at wikepedia articles too. I am using the insecure rom if that makes a difference.
What version should the browser be now?
I have 1.0.13.328_10008910
Gonna go clear data, etc.
Well, heck, that did it. Thanks for that. Interesting feature!

Flashed this succesfully... but i neglected to wipe the system and accidentally flashed the 4.0 gapps package after. Boots fine but i am getting an android.process.acore FC and a Calender session FC. Any suggestions? I came from JC's ICS build and I am thinking of just going back to that.
Update. Nevermind. Just went back to ICS. The Stock Launcher gives me douche chills.

Swype?
Anyone who has Swype working on 6.2.1 or 6.2.2 installed this? If so can you tell me what happened to your Swype and were you able to get it working again?
I'm still on 6.2.1 (updates blocked with Droidwall) and went through so much hassles getting everything working *just* right, I'm trying to decide if the changes in 6.3 are worth potentially having to re-do Swype, market, calendar/contact sync, etc.
Edit: Any hope for an incremental update on this one? I loved the ones for 6.2.1 and 6.2.2.
Edit2: Any issues with market or calendar/contact syncs (for those of us who had set that up)?

[Q] JB can't keep a recovery?

I just upgraded to JB, and like most of you, I've been adding things to it, mostly through CWM. The problem is, the recovery partition is (kinda) broken. Let me explain.
If I turn off my GNex and reboot it to Fastboot then use Fastboot to go to Recovery mode, or even try to boot to it from ROM manager, I get the "android on his back with his panel open and a <!> floating over him" icon. I have to pull the battery to get past that. From there, if I use the Galaxy Nexus Toolkit to flash a recovery, it will boot to it, but even if I reboot immediately, I get <!> again. If I flash CWM from ROM manager, it will work, but again, only that one time. It's like something in the shutdown process is breaking recovery.
I tried it with CWM, CWM Touch, and TWRP. Same problem.
Am I alone in this?
Is there a fix?

This happened to me after I flashed stock JB. I then flashed bigxie's rooted deodexed Rom and my recovery sticks

I am on Team Liquid vicious v2 w/ franco 200 kernel. it has been very smooth and I have been able to boot into recovery seamlessly.

I am assuming you already have root. Just go to the /system folder then rename recovery-from-boot.p to something else and cwm will stick

I've got the same problem from time to time.
Suddenly CWM is away and I have to reflash it.
Can I fix this by deleting the .p file mentioned?
Sent from my Galaxy Nexus using xda app-developers app

land.apfel said:
I've got the same problem from time to time.
Suddenly CWM is away and I have to reflash it.
Can I fix this by deleting the .p file mentioned?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Kinda weird that it's from "time to time" because if that file is there, then it should bring you back to stock recovery every time after you use your newly flashed temporary recovery. Yes, rename/delete that file and it should stick.

anton2009 said:
Kinda weird that it's from "time to time" because if that file is there, then it should bring you back to stock recovery every time after you use your newly flashed temporary recovery. Yes, rename/delete that file and it should stick.
Click to expand...
Click to collapse
Looks like deleting the files has worked soo far. Thanx
land.apfel

http://forum.xda-developers.com/showthread.php?p=28083666
Sent from my Galaxy Nexus using Tapatalk 2

[Q] Hyperdrive Installation problem

Hi guys, I've been trying to flash the new Hyperdrive RLS11 on my AT&T Galaxy s3 and no matter what I do, my phone says cant open and aborts the installation. I can never get the Aroma installer to start. I do factory reset, wipe cache, dalvik, and format system, but it fails every time. Any ideas?

Could be a bad download. You could try grabbing it again. Also, is your recovery up to date?

xBeerdroiDx said:
Could be a bad download. You could try grabbing it again. Also, is your recovery up to date?
Click to expand...
Click to collapse
I downloaded it from 3 different of his mirrors none of which worked. Im of the latest version of Clockwork mod. could it be the new update from 6.0.3 to 6.0.3.1 on clockwork? or should i use something other than clockwork

you should use twrp.. check the md5 of your download after you download it for accuracy. try that.. if it doesnt work u can always flash cwm again

Flash in twrp. Get twrp by downloading goo manager app and selecting install open recovery
Also are you grtiing a status 7 error?
Sent from my SAMSUNG-SGH-I747 using xda premium

For whatever reasons, sometimes when flashing in cwm or twrp, you will have issues and installing the other custom recovery will allow you to flash the desired ROM. you obviously then have the option to return to the custom recovery you were previously running either because you prefer it or all your backups were made in it.

Alright thanks ill try it tonight, hopefully it works
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

B.domonoski said:
Alright thanks ill try it tonight, hopefully it works
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Some ROm's are picky or you have a bad download. Issues with downloading that rom seem quite common. I tend to lean more towards android file host than anything.

i'm i nthe same situation for the past 2 days i have been trying to install it , i had the problem that after flash and reboot it will reboot back to recovery , today that seems not to be happening anymore now i'm getting stuck on boot animation and i have tried every step fix anytihng you can think of and no luck , i'm running now thw rls 10 with no problems but this rls 11 is driving me crazy i'm doing a redownload se if that helps in anyway

I used twrp and it worked fine! Thanks guys
Sent from my SCH-I605 using xda app-developers app

I used CWM without a problem
"You stay classy San Diego"

B.domonoski said:
I used twrp and it worked fine! Thanks guys
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
awesome. Glad it worked for you... it can be a picky, but gorgeous rom.

Similar problem
Hey guys
I've gone through all the steps as instructed, but can't install HD RSL15 successfully. I downloaded the installation file from a mac which then automatically unzips the folder. Zipped it back up with 7zip and threw it on the phone. I went through all the prescribed steps using TWRP 2.6 and AndroidUnite's video on youtube (How To Install TWRP Recovery And Flash Custom ROM) as example . This is the 2nd time Ive downloaded the file and I switched over from CWM based on this thread's recommendations.
When it comes to installing the ROM the window ends up looking like this:
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Error flashing zip...
Updating partition files...
FAILED
Have I done something wrong during the previous steps (flashing, installing recovery) or does it have something to do with the method of zipping the files (tried fastest and store as compression options, doing store makes the file unreadable by the phone during recovery mode)? Please help

Unable to Format /data

Hi all, this is my first post here. Unfortunately it is an issue, but I have been flashing roms for a while now.
So last night after flashing Ditto Note for my note 2 on att, I decided I didn't like it and wanted to revert back to my previous rom. However, when I am trying to format data in recovery it just hangs. I have tried both on CWM and TWRP... twrp says: "error too many open files"
And obviously this issue has caused many other issues for me such as being unable to flash anything else as anything else will just get stuck on the bootscreen.
I remember somewhere that there is a flashable zip that will specifically format everything for you, but I dont remember what this was called.
But any help would be great
Flashed stock 4.3 via Odin and it still doesn't boot past samsung screen

Just tried using zoot's super wipe
http://forum.xda-developers.com/showthread.php?t=1983489
and once again it is stuck on data wipe

xsnes said:
Hi all, this is my first post here. Unfortunately it is an issue, but I have been flashing roms for a while now.
So last night after flashing Ditto Note for my note 2 on att, I decided I didn't like it and wanted to revert back to my previous rom. However, when I am trying to format data in recovery it just hangs. I have tried both on CWM and TWRP... twrp says: "error too many open files"
And obviously this issue has caused many other issues for me such as being unable to flash anything else as anything else will just get stuck on the bootscreen.
I remember somewhere that there is a flashable zip that will specifically format everything for you, but I dont remember what this was called.
But any help would be great
Flashed stock 4.3 via Odin and it still doesn't boot past samsung screen
Click to expand...
Click to collapse
Did you make a backup or anything you can try to just do to maybe fix the bad files that didn't wanna delete
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

Yes I have tried doing a restore.
IN specifics this is the exact log I am getting from as soon as i start it up TWRP:
E:error opening '/data/data/com.google.android.marvin.talkback////////////////
//////////////////////
////////////////////
////////////////////
//////////////////
//////////////////
////////////////
//////////////////
////////
////
//
//
/
E: error: Too many open files
I tried deleting this folder from twrp file manager and the phone just reboots

In twrp try just deleting just that file maybe if you haven't already
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

I've tried TWRP and Aroma file manager now. Aroma file manager detected over 998 files in that folder until it froze... I've also tried moving the folder into my external SD card in which case there also happens to be 335 files until it froze as well.
How does a rom manage to install thousands of blank folders??

Are you able to flash a rom or you stuck at the recovery?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

terpin32 said:
Are you able to flash a rom or you stuck at the recovery?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes. I have flashed and booted into a Rom a couple times while having this 'data wipe' issue. However i feel like it is the luck of the draw because sometimes it boots, other times it hangs at the samsung screen lol
Should I go ahead and try to install a rom?

Is the "wipe" command issued by the recovery simply "rm -rf" or an actual format command with mkfs.ext4?

Darkshado said:
Is the "wipe" command issued by the recovery simply "rm -rf" or an actual format command with mkfs.ext4?
Click to expand...
Click to collapse
The logs say that it uses "make_ext4fs function"

Can I just go through the data folder with file explorer and delete everything else there?
OR is there another super wipe style zip that I don't know about ?

It probably won't let you
Sent from my GT-N7105 using XDA Premium 4 mobile app

solved
Issue has been solved. Wiped phone with a script? (i think) from a flashable zip contained from ANDROID HD rom for the note 2
for those that might need it: http://forum.xda-developers.com/showthread.php?t=2040941 (3rd post down)
This script does not use AROMA which has crashed for me everytime I tried to wipe with it. Really useful
Now currently running aosp rom cause I hate the new TW in 4.3 and 4.4 lol